---
id: "CVE-2026-130343"
page: "https://infrastack.ai/live/CVE-2026-130343"
kind: "vulnerability"
aliases: ["CVE-2026-130343"]
title: "phpMyFAQ: authenticated users can file account removal requests for others"
severity: "medium"
cvss: 5.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "phpmyfaq", "self-hosted"]
not_affected_if: ["no-user-accounts", "patched-version"]
published_at: "2026-11-17T02:17:15+00:00"
first_seen_at: "2026-11-17T02:40:30+00:00"
updated_at: "2026-11-17T02:42:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-130343", "first_seen_at": "2026-11-17T02:40:30+00:00"}]
exploit_sources: []
---

# phpMyFAQ: authenticated users can file account removal requests for others

Link for people: https://infrastack.ai/live/CVE-2026-130343 (this .md is for agents)

phpMyFAQ's user/request-removal endpoint checks ownership against the attacker-supplied user ID rather than the session user, so any logged-in user can file removal requests for other accounts. An attacker who knows a victim's login name and email can trigger a spoofed removal email to administrators, which may lead an admin to delete the victim's account and data.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed phpMyFAQ version in the admin panel or `composer show phpmyfaq/phpmyfaq`
- Confirm whether the installation is on a 3.2.x, 4.1.x before `4.1.12`, or 4.2.0-alpha/RC before `4.2.0-RC.2` release

## Fix

- phpMyFAQ 4.1.x: move to `4.1.12`
- phpMyFAQ 4.2.x: move to `4.2.0-RC.2`
- phpMyFAQ 3.2.x: unknown

## Timeline

- 2026-11-17T02:40:30+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-130343

## Documents

- [advisory] Vendor advisory: github.com https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-42c6-wxqw-2rv6
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/phpmyfaq-3.2.5-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-authorization-bypass-via-request-removal
- [fix] Patch: github.com https://github.com/thorsten/phpMyFAQ/commit/30997574d7c00b4e2d7121cf1653fb244c63dd9e
- [fix] Release notes: github.com https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.12
- [fix] Release notes: github.com https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2

## From the sources

phpMyFAQ 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the user/request-removal API endpoint that lets authenticated users file account removal requests as other users. The ownership check calls getUserById() with the attacker-supplied userId on the session user object, so it compares the input against the target's own record. Attackers who know a victim's login name and email can submit that userId, loginname, and email, sending administrators a spoofed Remove User Request email. This may lead an admin to delete the victim's account and data.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
