/

CVE-2026-56396

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-862) in phpMyFAQ User Admin

CVE-2026-56396

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Privilege Escalation to SuperAdmin

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

phpMyFAQ contains missing authorization checks in user management endpoints that allow lower-privileged admins to escalate their privileges.

When an authenticated admin with edit_user capabilities can modify the is_superadmin flag or user rights without further checks, they may gain full SuperAdmin access.

Affected context

This vulnerability occurs in phpMyFAQ deployments where the application exposes administrative user-management functions, such as editUser() and updateUserRights(), to roles below full SuperAdmin.

In affected versions, the backend trusts that any user with general edit_user permissions is allowed to change critical properties, including the is_superadmin flag and arbitrary access rights, without revalidating their own privilege level.

Exploit preconditions

  • Attack surface: Authenticated administrative web interface (user management pages or APIs)
  • Required access: Valid phpMyFAQ account with non-SuperAdmin role but granted edit_user or similar user-edit permissions
  • Trigger point: Invoking editUser() or updateUserRights() endpoints and modifying sensitive fields such as is_superadmin or high-privilege rights
  • Why exploitation is possible: The application performs no additional authorization check to ensure that only existing SuperAdmins may assign or elevate to SuperAdmin privileges, allowing privilege escalation by mid-level admins

Why this happens

The underlying issue is a missing authorization step on sensitive administrative operations, mapping directly to CWE-862: Missing Authorization.

The code assumes that having a generic permission like edit_user is sufficient to modify all aspects of a user account, including high-impact fields that control global privileges and SuperAdmin status.

Instead of enforcing fine-grained checks or revalidating the caller's role before allowing changes to is_superadmin and critical rights, the implementation treats all edit-user actions as equivalent, creating an insecure privilege boundary.

Potential impact

  • Non-SuperAdmin administrators can escalate themselves to SuperAdmin level
  • Attackers controlling such an account can gain full control over phpMyFAQ configuration and content
  • Unauthorized changes to user rights and roles across the system can occur
  • Potential exposure or deletion of knowledge base content and configuration data
  • Indirect impact on integrated systems if phpMyFAQ is used as part of a wider administrative stack

General mitigation guidance

Mitigation typically focuses on tightening authorization checks around sensitive administrative actions.

Common patterns include:

  • Enforcing role-based checks that only existing SuperAdmins may grant or revoke SuperAdmin status or high-privilege rights
  • Implementing field-level authorization, where critical attributes like is_superadmin require stronger permissions than general user edits
  • Applying defense-in-depth by re-verifying the caller's role server-side on every privileged update, regardless of client-side UI restrictions
  • Reducing the number of accounts with user-edit capabilities and applying the principle of least privilege
  • Introducing approval workflows or dual-control for privilege changes in environments with strict governance requirements

How teams detect issues like this

Detection efforts can focus on both code and operational signals:

  • Static analysis and code review looking for admin endpoints that modify roles, flags, or permissions without explicit role checks
  • Reviewing controller or service methods that update is_superadmin, roles, or rights to ensure they reference centralized authorization logic
  • Implementing logging and monitoring for changes to administrator accounts and privilege assignments, with alerts on unexpected role escalations
  • Using security scanning tools or policy-as-code checks to flag endpoints where high-privilege fields are updated based solely on generic edit permissions

Sources

SourceLink
github.comgithub.com/thorsten/phpMyFAQ/security/advisories/GHSA-985r-q3qp-299h
vulncheck.comvulncheck.com/advisories/phpmyfaq-privilege-escalation-via-missing-authorization-in-edituser-and-updateuserrights

Frequently asked

questions

It is highly exploitable in environments where non-SuperAdmin users legitimately have edit_user permissions. Any such user could leverage the missing checks to elevate themselves to SuperAdmin without needing additional vulnerabilities.

No. Exploitation occurs entirely through the authenticated web interface or corresponding HTTP endpoints, as long as the attacker has a lower-privileged administrative account with user-edit capabilities.

Centralize and enforce explicit authorization checks for all high-impact operations, especially those involving role changes, permission grants, and SuperAdmin flags, ensuring that only appropriately privileged roles can perform such actions.

Design and implement a clear role and permission model, enforce field-level checks on sensitive attributes, mandate security-focused code reviews for administrative features, and use automated tests or policies to ensure every privileged endpoint performs appropriate authorization.

Find out what's already
exploitable in your codebase.