Skip to main content

phpMyFAQ CVE-2026-57995

| EUVDEUVD-2026-40454 HIGH
Improper Privilege Management (CWE-269)
2026-06-30 VulnCheck GHSA-996g-x95h-p2f5
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as GROUP_EDIT delegated admin
  2. Delivery
    Open group permissions editor
  3. Exploit
    Submit updatePermissions assigning admin rights to own group
  4. Execution
    Server skips self-rights check
  5. Persist
    Inherit elevated rights via group membership
  6. Impact
    Full administrative control of phpMyFAQ

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

Exploitation requires an authenticated phpMyFAQ administrator who holds the GROUP_EDIT permission (PR:L) and is a member of, or can target, a group whose permissions they can edit; the attacker then assigns rights they do not themselves possess via the GroupController::updatePermissions handler. There is no requirement for user interaction (UI:N) or special attack conditions (AT:N), and the admin interface must be network-reachable (AV:N). The principal limiting factor is that fully locked-down deployments which never delegate the GROUP_EDIT right to less-trusted accounts are not practically exploitable, since a full super-admin already has the privileges this flaw would grant.

Impact

The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, VC/VI/VA:H, score 8.7) describes a network-exploitable, low-complexity attack requiring an existing low-privileged authenticated account (the GROUP_EDIT delegated admin) and yielding full confidentiality, integrity, and availability impact on the application - consistent with complete admin takeover. The PR:L requirement is the principal limiting factor: this is not an anonymous internet attack but an insider/over-delegation escalation, so realistic risk concentrates in deployments that actually hand out partial admin rights. No EPSS score, SSVC decision, or KEV entry was provided, and no POC is referenced; absence of those signals plus the authentication prerequisite suggests this is a meaningful but not mass-exploited issue. There is no conflict between the vector and description - both point to an authenticated, remotely reachable privilege-escalation primitive.

Exploit ScenarioDerived

A company grants a help-desk lead a phpMyFAQ admin account limited to the GROUP_EDIT capability for managing FAQ author groups. That user opens the group-permissions editor, assigns full administrative rights to a group they are a member of, and reloads - inheriting super-admin control over the entire knowledge base. No public POC is referenced, but the attack needs only the existing low-privileged session and a single crafted permission-update request.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 30, 2026

Privilege escalation in phpMyFAQ before 4.1.5 lets a delegated administrator holding the GROUP_EDIT right elevate to full administrative control. Because GroupController::updatePermissions never verifies that the caller already possesses the permissions being assigned, a low-privileged admin can grant high-value rights to a group they belong to and inherit those rights. The flaw was reported by VulnCheck; no public exploit identified at time of analysis, and it is not listed in CISA KEV.

RemediationAI

Vendor-released patch: phpMyFAQ 4.1.5 - upgrade to 4.1.5 or later as the primary fix, per the GHSA advisory (https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-pg62-f8g4-4wqh). If immediate upgrade is not possible, reduce exposure by revoking the GROUP_EDIT right from all delegated/non-trusted administrators so that group-permission editing is restricted to fully trusted super-admins (trade-off: removes legitimate delegated group management until patched), and audit existing group permission assignments for unexpected high-value rights that may indicate prior abuse. Restricting admin-panel access to a trusted network segment or VPN further limits who can reach the vulnerable controller, at the cost of remote administrative convenience.

Affected VersionsENISA

phpMyFAQ 0 <4.1.5

Affected Packages

composer phpmyfaq/phpmyfaq fix: 4.1.5
composer thorsten/phpmyfaq fix: 4.1.5
euvd phpmyfaq fix: 4.1.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in composer, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

phpMyFAQ is an open-source PHP-based FAQ/knowledge-base application with a role- and group-based permission model where administrators can be delegated narrow capabilities such as GROUP_EDIT. The root cause is CWE-269 (Improper Privilege Management): the updatePermissions handler in GroupController applies whatever permission set is submitted for a group without enforcing a self-rights constraint - i.e. it does not check that the acting administrator currently holds each right they are attempting to assign. Permissions in phpMyFAQ are effectively transitive through group membership, so any right written onto a group is inherited by its members, turning a missing authorization check into a direct path to higher privilege.

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

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.8 HIGH

Remotely reachable admin function (AV:N/AC:L), needs an existing GROUP_EDIT admin account so PR:L, no user interaction, and full app compromise gives C/I/A:H with unchanged scope.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Jul 01, 2026 - 02:16 EUVD

DescriptionCVE.org

phpMyFAQ before 4.1.5 contains a privilege escalation vulnerability in GroupController::updatePermissions that allows GROUP_EDIT administrators to grant arbitrary rights to groups without verifying they hold those rights themselves. A delegated administrator can exploit this by assigning high-value permissions to a group they belong to, inheriting those rights and escalating privileges up to full administrative control.

Executive ViewAI

Why It Matters

phpMyFAQ versions before 4.1.5 contain a privilege escalation vulnerability (CVSS 8.7) allowing authenticated administrators with GROUP_EDIT permissions to escalate to full administrative control. No public exploit has been identified at time of analysis. Organizations using phpMyFAQ face insider threat risk, as delegated administrators could gain unrestricted system access, potentially enabling unauthorized FAQ modification, data exposure, or system reconfiguration.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: minimize GROUP_EDIT role assignment to trusted personnel only, enable detailed audit logging and real-time alerting for group permission changes, conduct monthly access reviews of delegated administrators, implement change approval workflows for sensitive permission modifications, and consider network segmentation for phpMyFAQ administrative interfaces.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Low
niche open-source PHP FAQ application, limited enterprise footprint
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2025-59943 CRITICAL POC
9.8 Oct 03

Duplicate-email registration handling in phpMyFAQ 4.0.7 through 4.0.13 (and 4.0-nightly-2025-10-03 and earlier) lets una

CVE-2023-5865 CRITICAL POC
9.8 Oct 31

Insufficient Session Expiration in GitHub repository thorsten/phpmyfaq prior to 3.2.2. Rated critical severity (CVSS 9.8

CVE-2023-1886 CRITICAL POC
9.8 Apr 05

Authentication Bypass by Capture-replay in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity

CVE-2023-1753 CRITICAL POC
9.8 Mar 31

Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity (CVSS 9.8), t

CVE-2022-3754 CRITICAL POC
9.8 Oct 29

Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.8. Rated critical severity (CVSS 9.8), th

CVE-2026-46364 CRITICAL POC
9.3 May 15

Unauthenticated SQL injection in phpMyFAQ before 4.1.2 allows remote attackers to extract credentials, admin tokens, and

CVE-2017-15730 HIGH POC
8.8 Oct 22

In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.ratings.php. Rated high severity (CVS

CVE-2017-15808 HIGH POC
8.8 Oct 23

In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php. Rated high severity (CVSS 8.8), this vulnerability is

CVE-2017-15735 HIGH POC
8.8 Oct 22

In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for modifying a glossary. Rated high severity (CVSS

CVE-2017-15734 HIGH POC
8.8 Oct 22

In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.main.php. Rated high severity (CVSS 8

CVE-2024-28107 HIGH POC
8.8 Mar 25

phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Rated high severi

CVE-2024-27299 HIGH POC
8.8 Mar 25

phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Rated high severi

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy