Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as non-superadmin admin with GROUP_EDIT
-
ExploitCall updatePermissions to write unrestricted group grant
-
ExecutionSelf-join group via updateMembers endpoint
-
ImpactGain site-wide FAQ edit and publish rights
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated non-superadmin administrator account that holds the GROUP_EDIT right (PR:H). The flaw lives specifically in the group permission API's updatePermissions and updateMembers endpoints, which validate held rights without checking language or category scope and then write unrestricted group grants. Exploitation is only meaningful in deployments that use delegated/scoped administration - i.e., where lower-tier admins are intentionally limited to specific languages or categories; a single-superadmin installation offers no privileges to escalate from. Limiting factors: attacker must already possess GROUP_EDIT, superadmin is not required but a scoped admin account is, and only phpMyFAQ builds from 4.2.0-alpha.2 up to (not including) 4.2.0-beta are affected. |
| Impact | This is a moderate-severity, authenticated privilege-escalation flaw (CVSS 4.0 base 7.0) whose real-world risk is tempered by its PR:H prerequisite. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N) confirms the attacker must already hold high privileges - specifically a non-superadmin administrator account with the GROUP_EDIT right - so this is an insider or post-compromise escalation path, not a remote-unauthenticated breach. Impact is skewed toward integrity (VI:H: unrestricted FAQ create/edit/publish across all languages and categories) with only low confidentiality (VC:L) and no availability impact. No EPSS score, CISA KEV listing, or public POC is present in the provided intelligence, so exploitation status is: no public exploit identified at time of analysis. The signals are internally consistent - there is no conflict between the network attack vector and the described web-API exploitation, since the GROUP_EDIT administrator reaches the vulnerable updatePermissions/updateMembers endpoints over HTTP. Net: a credible but conditional risk that matters most in multi-tenant or delegated-administration phpMyFAQ deployments where lower-tier admins are deliberately scoped to narrow language/category permissions; in single-superadmin installations the practical exposure is minimal. Missing EPSS and absence from KEV suggest this is not under active or widespread exploitation. |
| Exploit ScenarioDerived | A multi-author phpMyFAQ site delegates content administration by giving a department admin the GROUP_EDIT right scoped to a single language or category. That admin calls the updatePermissions endpoint to grant a group a right they only legitimately hold in that narrow scope, then uses updateMembers to add their own account to that group, obtaining unrestricted FAQ create, edit, and publish access across every language and category. No public exploit code is identified at time of analysis, though the attack requires only standard authenticated API calls over the network (AV:N/AC:L). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 17, 2026
Privilege escalation in phpMyFAQ builds from 4.2.0-alpha.2 up to but not including 4.2.0-beta allows a non-superadmin administrator who holds GROUP_EDIT to abuse the group permission API's updatePermissions and updateMembers endpoints, grant a group rights beyond the attacker's language or category scope, and self-join that group to obtain unrestricted FAQ create, edit, and publish access across all languages and categories. The CVSS 4.0 base score is 7.0, but exploitation requires an authenticated scoped administrator account and is only meaningful in deployments that use delegated administration limited by language or category, since a single-superadmin installation offers no scoped boundary to escalate from. No public exploit identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade phpMyFAQ to 4.2.0-beta or later; 4.2.0-beta is the first release at or beyond the fixed boundary, and the vendor advisory is https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6vf7-mrj2-7c37. If immediate upgrade is not possible, remove GROUP_EDIT from every non-superadmin role or restrict group-permission administration to superadmins until the patch is applied, with the trade-off that delegated group management stops working for those accounts. Audit existing groups, group memberships, and language/category grants for unexpected broad permissions or self-joined groups, and review logs for calls to the updatePermissions and updateMembers endpoints from scoped administrators. The VulnCheck advisory at https://www.vulncheck.com/advisories/phpmyfaq-from-4.2.0-alpha.2-before-4.2.0-beta-privilege-escalation-via-group-permissions-api provides additional reference.
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
phpMyFAQ is a PHP-based FAQ and knowledge-base application; the provided CPE is cpe:2.3:a:thorsten:phpmyfaq:*:*:*:*:*:*:*:*, with the description narrowing affected releases to 4.2.0-alpha.2 up to but not including 4.2.0-beta. The root cause is CWE-269 (Improper Privilege Management): the group permission API's updatePermissions and updateMembers endpoints check whether the caller holds a right but do not constrain that check to the language or category scope in which the right was granted, and they then persist unrestricted group-level grants. A non-superadmin administrator with GROUP_EDIT can therefore convert a narrowly scoped right into a global group grant and join the group through updateMembers, escalating to FAQ create, edit, and publish access across all languages and categories. The coordinated CVSS 4.0 vector is AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N (base 7.0), while the independent CVSS 3.1 assessment is AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N, reflecting a high-privilege authenticated attacker with limited confidentiality impact and high integrity impact.
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:L/VI:H/VA:N/SC:N/SI:N/SA:N
Exploitation needs an authenticated admin with GROUP_EDIT so PR:H; endpoints are reachable over HTTP with no special timing (AV:N/AC:L); impact is high integrity (content publish) with low confidentiality and no availability.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-beta contains a privilege escalation vulnerability in the group permission API, whose updatePermissions and updateMembers endpoints check held rights without regard to language or category scope and write unrestricted group grants. Non-superadmin administrators holding GROUP_EDIT can grant a group a right they hold only in a narrow scope and self-join it via updateMembers, gaining unrestricted FAQ create, edit, and publish access across all languages and categories.
Technical POC Analysis
CWE-269 (Improper Privilege Management), implemented as a scope-blind delegation guard followed by an unrestricted grant.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
phpMyFAQ versions 4.2.0-alpha.2 through before 4.2.0-beta contain a privilege escalation flaw that lets a scoped administrator with GROUP_EDIT bypass delegated language and category boundaries to gain unrestricted FAQ content control. Organizations using delegated administration are most exposed because the flaw undermines least-privilege governance and could allow unauthorized content changes across all languages and categories. No public exploit has been identified, but leadership should prioritize inventory and access review given the absence of a vendor patch.
No vendor-released patch identified at time of analysis. Restrict GROUP_EDIT to trusted administrators; audit group memberships and permission scopes; monitor updatePermissions and updateMembers API calls; temporarily disable delegated group management or the group permission API if feasible; enforce least privilege and separate scoped admin roles.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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-103328
GHSA-vj43-979m-cpx8
NVD
CVE.org
EPSS
VulDB
Exploit-DB