Authorization bypass in phpMyFAQ lets users remove other accounts
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
phpMyFAQ from 3.2.5 before 4.1.12 and from 4.2.0-alpha before 4.2.0-RC.2 has an authorization bypass in the user/request-removal API endpoint. The ownership check compares an attacker-supplied userId against the target's own record, a flaw tied to CWE-639. An authenticated user with low privileges can file account removal requests as other users, and an attacker who knows a victim's login name and email can send administrators a spoofed Remove User Request email, which may lead an admin to delete the victim's account and data.
Written with Claude Haiku 5.5 from the sources below · 2026-11-17
Description from the CNA
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
Upgrade phpMyFAQ to version 4.1.12 or 4.2.0-RC.2. The sources list no fixed version for phpMyFAQ 3.2.5 or earlier 3.x releases.
Written with Claude Haiku 5.5 from the sources below · 2026-11-17
- Fix · CNA phpMyFAQ (thorsten) Fixed in 4.1.12, 4.2.0-RC.2
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
thorsten phpMyFAQ 4.1.12, 4.2.0-RC.2
16 records Highest priority Priority MEDIUM 8 MEDIUM, 8 LOW
Other records, highest priority first
- TI-2026-92399 Authentication bypass in phpMyFAQ web installer allows unauthenticated reinstallPriority MEDIUM 55
- TI-2026-92397 Authorization bypass in phpMyFAQ lets attackers overwrite passkeysPriority MEDIUM 55
- TI-2026-92390 Account enumeration via WebAuthn prepare in phpMyFAQPriority MEDIUM 46
Timeline
- 2026-11-17 Threatist record created from CVE-2026-130343
- 2026-11-17 Alias added: GHSA-mmjf-pc5j-8xpr
References
More thorsten vulnerabilities
- TI-2023-00296 Improper Authentication in thorsten/phpmyfaq CVSS 3.1CRITICAL 9.8
- TI-2026-76118 Authentication bypass in phpMyFAQ via WebAuthn credential injection CVSS 4.0CRITICAL 9.3
- TI-2026-32868 phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint CVSS 4.0CRITICAL 9.3
- TI-2026-76108 Unauthenticated denial of service in phpMyFAQ API pagination CVSS 4.0HIGH 8.7
- TI-2026-53313 phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP CVSS 4.0HIGH 8.8
- TI-2026-34083 phpMyFAQ - Unauthenticated Information Disclosure via getIdFromSolutionId Permission Bypass CVSS 4.0HIGH 8.7
Sources
- CVE-2026-130343 · CVE Program
- CVE-2026-130343 · NVD
- GHSA-mmjf-pc5j-8xpr · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences