CVE-2026-111908

8.3High

Published 17 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

8.3High

Attack vector: Network
Complexity: Low
Privileges needed: Low
User interaction: None
Impact: High impact on confidentiality, integrity
Weakness: CWE-639

Impact

Authenticated users with the edit_faq permission can view, alter, and publish restricted FAQs they normally cannot access. Attackers need network access and an account with basic FAQ editing rights.

Root cause

The PUT /api/v3.1/faq/update endpoint checks only the global edit_faq permission rather than verifying access rights for the specific target FAQ ID.

Affected systems

phpMyFAQ 4.0.0 before 4.1.9, and 4.2.0-alpha before 4.2.0-beta

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Fix & remediation

Upgrade to phpMyFAQ 4.1.9 or 4.2.0-beta. If you cannot patch immediately, block or restrict access to the PUT /api/v3.1/faq/update endpoint at your reverse proxy or web server.

shell

$ composer update phpmyfaq/phpmyfaq

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

phpMyFAQ 4.0.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains a broken object-level authorization vulnerability in the PUT /api/v3.1/faq/update endpoint, which checks only the global edit_faq permission and does not verify access to the target FAQ. Authenticated users with edit_faq permission can supply the ID of a restricted FAQ they cannot view to modify its content, bypass moderation, and change its publication state.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-111908