CVE-2026-130343
Deferred Deferred - Pending Action

Authorization Bypass in phpMyFAQ User Removal API

Vulnerability report for CVE-2026-130343, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.12 (exc)
phpmyfaq phpmyfaq to 4.2.0-rc.2 (exc)
thorsten phpmyfaq to 4.1.12 (exc)
thorsten phpmyfaq to 4.2.0-rc.2 (exc)
thorsten phpmyfaq 4.1.12
thorsten phpmyfaq 4.2.0-rc.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in phpMyFAQ versions 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 allows authenticated users to submit account removal requests for other users by exploiting a flawed ownership check. The system incorrectly compares the attacker-supplied user ID against the session user's own record instead of the intended victim's record, enabling spoofed removal requests.

Detection Guidance

To detect this vulnerability, check if your phpMyFAQ instance is running a vulnerable version (3.2.5 before 4.1.12 or 4.2.0-alpha before 4.2.0-RC.2). Inspect the UserController.php file for improper user ID validation in the request-removal endpoint. Look for the use of getUserById() without proper session binding.

Impact Analysis

An attacker who knows a victim's login name and email can trick an administrator into deleting the victim's account and data by submitting a spoofed removal request. This could lead to data loss for the victim, though the attack requires admin action to complete.

Compliance Impact

This vulnerability could lead to unauthorized account deletion, potentially violating data protection requirements under GDPR or HIPAA by exposing or mishandling user data. Unauthorized deletions may also conflict with audit or retention policies.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.1.12 or later. If upgrading is not immediately possible, apply the patch from the commit 30997574d7c00b4e2d7121cf1653fb244c63dd9e which introduces proper session validation. Ensure removal requests are validated against the current user's session data only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130343. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...