PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-45007 thorsten CVE debrief

CVE-2026-45007 is an access-control flaw in phpMyFAQ before 4.1.2. In ConfigurationTabController.php, 12 /admin/api/configuration endpoints used userIsAuthenticated() instead of userHasPermission(CONFIGURATION_EDIT), so any authenticated user could query configuration metadata such as the permission model, cache backend, mail provider, and translation provider. The issue is confidentiality-only, but it weakens least-privilege controls and can expose useful internal details.

Vendor
thorsten
Product
phpmyfaq
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-15
Original CVE updated
2026-05-28
Advisory published
2026-05-15
Advisory updated
2026-05-28

Who should care

phpMyFAQ operators, administrators, and developers who maintain admin API authorization checks should care most. Security teams should also review any environment where authenticated non-admin users can reach phpMyFAQ administrative endpoints.

Technical summary

The supplied source material describes a missing permission check in phpMyFAQ's ConfigurationTabController.php. Rather than requiring CONFIGURATION_EDIT, 12 endpoints accepted any authenticated session via userIsAuthenticated(), enabling authenticated users to enumerate configuration metadata over /admin/api/configuration. The supplied CVSS vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, which matches a network-reachable, low-complexity disclosure issue with no integrity or availability impact.

Defensive priority

Medium priority. The flaw does not grant direct code execution or write access, but it exposes internal configuration details to any authenticated user and can undermine least-privilege assumptions. Upgrade promptly if you run affected phpMyFAQ versions and verify that admin endpoints enforce the intended permission check.

Recommended defensive actions

  • Upgrade phpMyFAQ to 4.1.2 or later.
  • Verify that /admin/api/configuration endpoints enforce userHasPermission(CONFIGURATION_EDIT) rather than only checking authentication.
  • Review other admin controllers for similar authentication-vs-authorization mistakes.
  • Confirm that no non-admin authenticated accounts can reach sensitive configuration APIs in production.
  • Monitor logs for unusual access to /admin/api/configuration endpoints.
  • Reassess any operational assumptions that depended on configuration metadata being restricted to administrators.

Evidence notes

The supplied NVD record identifies the vulnerability as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N and lists the status as Deferred. The referenced GitHub advisory and VulnCheck advisory both describe the same root cause: a missing permission check in ConfigurationTabController.php affecting 12 configuration API endpoints and allowing information disclosure of system configuration metadata to authenticated users.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-45007 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-45007

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-45007 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45007

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-rm98-82fr-mcfx

    [email protected]

  • Source reference

    Unverified legacy reference

    URL: https://www.vulncheck.com/advisories/phpmyfaq-missing-permission-check-on-12-configuration-api-endpoints-allows-information-disclosure

    [email protected]

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.