Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as delegated admin with user-management rights
-
ExploitRequest GET /admin/api/user/data/{SuperAdminId}
-
ExecutionRead returned faquserdata TOTP secret
-
ImpactGenerate valid TOTP codes and bypass 2FA to escalate
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires an authenticated phpMyFAQ backend account that holds delegated user-management rights (PR:H) - anonymous or unauthenticated access is not sufficient, and this is the primary limiting factor. The specific trigger is calling the admin API endpoint GET /admin/api/user/data/{userId} with an arbitrary target userId; the endpoint performs no SuperAdmin or protected-target authorization check, so any such delegated admin can read any user's full faquserdata row (including the live TOTP secret). No special non-default configuration is needed beyond the existence of at least one additional privileged administrator whose data is worth stealing; affected versions are 3.2.0 before 4.1.9 and the 4.2.0 pre-release line before 4.2.0-beta. |
| Impact | This is a genuine but privilege-gated risk rather than a mass-exploitation emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N, score 7.0 HIGH) confirms the attack is network-reachable with low complexity and no user interaction, but PR:H means an attacker must already hold a privileged (delegated administrator with user-management rights) backend account - this is the single most important limiting factor. No EPSS score, CISA KEV listing, or POC indicator was supplied in the input, so there is no signal of active or widespread exploitation (no public exploit identified at time of analysis). The practical danger is the vulnerability's effect: an IDOR (CWE-639) that leaks a SuperAdmin's live TOTP secret, enabling a lower-privileged admin to escalate by bypassing two-factor authentication - the real-world impact (privilege escalation / 2FA bypass) is more severe than the modest 7.0 base score suggests, because it defeats a key compensating control. Note a mild internal tension: the supplied 4.0 vector assigns VI:L/VA:L, yet the described endpoint only returns data (a read-only information disclosure), so the direct integrity/availability impact is arguably none and the primary impact is confidentiality - verify with vendor/NVD. Priority should be MEDIUM-HIGH for any organization running multi-administrator phpMyFAQ deployments with delegated roles, and lower where only a single trusted SuperAdmin exists. |
| Exploit ScenarioDerived | A delegated administrator who has been granted only user-management rights (not SuperAdmin) issues an authenticated GET request to /admin/api/user/data/{userId} for the SuperAdmin's user ID. The response returns the full faquserdata row including the live TOTP secret, which the attacker loads into any TOTP generator to produce valid one-time codes and log in as SuperAdmin, bypassing 2FA. No public exploit identified at time of analysis, but the attack requires only a single crafted authenticated HTTP request and no special tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 17, 2026
phpMyFAQ versions 3.2.0 through 4.1.8 and the 4.2.0-alpha pre-release line before 4.2.0-beta expose an insecure direct object reference in the admin API endpoint GET /admin/api/user/data/{userId}, allowing a delegated administrator with user-management rights to read another user's full faquserdata row, including a live TOTP secret. The flaw is privilege-gated rather than anonymously exploitable: an attacker must already hold an authenticated backend account with delegated user-management permissions, but can then undermine two-factor authentication for a targeted privileged account by generating valid TOTP codes. No public exploit identified at time of analysis; the primary risk is to installations that delegate user administration to non-SuperAdmin accounts.
RemediationAI
Vendor-released patch: upgrade to phpMyFAQ 4.1.9 or 4.2.0-beta. If immediate upgrade is not possible, remove user-management permissions from delegated administrator accounts until patching is complete, and use a reverse-proxy or WAF rule to deny non-SuperAdmin access to /admin/api/user/data/*; both controls reduce exposure but can break legitimate delegated user administration. If exposure is suspected, rotate TOTP secrets and re-enroll affected privileged accounts, which requires user interaction, and review admin API access logs for unexpected reads of other users' faquserdata. See the vendor advisory at https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-hp8j-w94m-j5c7.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is phpMyFAQ's administrative REST API, and CPE data maps the affected package to thorsten:phpmyfaq. CWE-639 describes an authorization bypass through a user-controlled key: the {userId} path parameter is trusted as the object selector without verifying that the requester is a SuperAdmin or that the target account is protected from delegated administration. The endpoint returns the full faquserdata row, which contains the live TOTP secret used for two-factor authentication, so the confidentiality impact is high even though the assessed vector limits integrity and availability impact (C:H/I:N/A:N). The core weakness is missing object-level authorization on a privileged API path, not a cryptographic flaw in TOTP itself.
Know when Phpmyfaq gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N
Requires a privileged delegated-admin account (PR:H) over the network with no user interaction; endpoint only discloses data (TOTP secret), so C:H and I:N/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
phpMyFAQ 3.2.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains an insecure direct object reference vulnerability in GET /admin/api/user/data/{userId}, which returns any user's full faquserdata row, including the live TOTP secret, without a SuperAdmin or protected-target check. Delegated administrators with user-management rights can read a SuperAdmin's TOTP secret and generate valid codes to bypass two-factor authentication.
Technical POC Analysis
CWE-639 (authorization bypass through user-controlled key), with the advisory also tagging CWE-200 and CWE-522.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
phpMyFAQ's admin API permits a delegated user administrator to pull other accounts' stored profile records, including live two-factor secrets, so a single insider or compromised delegated account can quietly defeat MFA on privileged users. The exposure is concentrated in organizations that extend user-management rights beyond SuperAdmin - helpdesk, HR, or IT coordinators - and no vendor patch is currently available. Leadership should treat this as an identity-governance and insider-risk issue rather than an external perimeter threat.
No vendor patch identified at time of analysis. Restrict user-management delegation to SuperAdmin accounts only, remove delegated user-admin rights from all non-essential accounts, rotate and re-enroll TOTP secrets for privileged users whose records were reachable, monitor and alert on GET /admin/api/user/data/{userId} for cross-user access, and apply a WAF or reverse-proxy rule to block mismatched requester/target user IDs until a fixed release is validated.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Duplicate-email registration handling in phpMyFAQ 4.0.7 through 4.0.13 (and 4.0-nightly-2025-10-03 and earlier) lets una
Insufficient Session Expiration in GitHub repository thorsten/phpmyfaq prior to 3.2.2. Rated critical severity (CVSS 9.8
Authentication Bypass by Capture-replay in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity (CVSS 9.8), t
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.8. Rated critical severity (CVSS 9.8), th
Unauthenticated SQL injection in phpMyFAQ before 4.1.2 allows remote attackers to extract credentials, admin tokens, and
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.ratings.php. Rated high severity (CVS
In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php. Rated high severity (CVSS 8.8), this vulnerability is
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for modifying a glossary. Rated high severity (CVSS
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.main.php. Rated high severity (CVSS 8
phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Rated high severi
phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Rated high severi
EUVD-2026-103315
GHSA-44gp-7cgr-6p92
NVD
CVE.org
EPSS
VulDB
Exploit-DB