PatchSiren cyber security CVE debrief
CVE-2026-111908 thorsten CVE debrief
CVE-2026-111908 is a high-severity vulnerability in phpMyFAQ, a popular open-source FAQ management system. The vulnerability has a CVSS score of 8.7 and is classified as a broken object-level authorization issue. It affects phpMyFAQ versions 4.0.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta. An authenticated user with the edit_faq permission can exploit this vulnerability to modify the content of a restricted FAQ, bypass moderation, and change its publication state.
- Vendor
- thorsten
- Product
- phpMyFAQ
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-17
- Original CVE updated
- 2026-10-17
- Advisory published
- 2026-10-17
- Advisory updated
- 2026-10-17
Who should care
Defenders who manage phpMyFAQ installations, especially those with authenticated users who have the edit_faq permission, should be aware of this vulnerability and take steps to mitigate it.
Why it matters
CVE-2026-111908 is a high-severity vulnerability in phpMyFAQ that allows authenticated users with edit_faq permission to modify restricted FAQ content, bypass moderation, and change publication state. Defenders should prioritize patching or mitigating this vulnerability, especially in environments where authenticated users have the edit_faq permission.
- Authenticated users with edit_faq permission can modify restricted FAQ content
- Bypassing moderation and changing publication state is possible
- Patching or mitigating this vulnerability is a high priority
- Verification of user permissions and FAQ access controls is necessary
Technical summary
The vulnerability is caused by a broken object-level authorization issue in the PUT /api/v3.1/faq/update endpoint of phpMyFAQ. The endpoint checks only the global edit_faq permission and does not verify access to the target FAQ. This allows authenticated users with the edit_faq permission to modify the content of a restricted FAQ, bypass moderation, and change its publication state. Affected product deployments should be reviewed for exposure, and defenders should prioritize patching or mitigating this vulnerability, especially in environments where authenticated users have the edit_faq permission.
Defensive priority
Defenders should prioritize patching or mitigating this vulnerability, especially in environments where authenticated users have the edit_faq permission.
Recommended defensive actions
- Patch or upgrade phpMyFAQ to a version that is not vulnerable
- Restrict the edit_faq permission to trusted users
- Monitor for suspicious activity on the FAQ system
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability is described in the CVE Program record and the NVD vulnerability detail page. Additional information is available from source references, including a GitHub advisory and a Vulncheck advisory.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-111908 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-111908
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-111908 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-111908
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-j3px-r7cr-r26r
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/phpmyfaq-4.0.0-before-4.1.9-and-4.2.0-alpha-before-4.2.0-beta-bola-in-faq-update-via-rest-api
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.