# CVE-2026-111902: phpMyFAQ authorization bypass in FAQ access check

Source: https://junglewise.ai/threats/cve-2026-111902-phpmyfaq-4-2-0-alpha-before-4-2-0-beta-contains-an-authorization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-17. Updated: 2026-10-17  
License: CC BY 4.0 with a link back

CVE-2026-111902 · Severity: medium · CVSS 5.3 · Published 2026-10-17

phpMyFAQ is a FAQ management system that stores content in multiple languages and controls access based on publication status and ACLs. An authorization bypass in the isFaqAccessibleForUser() function allows unauthenticated attackers to read comments and attachment metadata from unpublished or restricted FAQs by manipulating the Accept-Language header. This bypasses access controls intended to hide draft or restricted content from public users.

Technologies: [Thorsten phpMyFAQ](https://junglewise.ai/threats/technologies/phpmyfaq). Vendors: [Thorsten](https://junglewise.ai/threats/vendors/thorsten).

## Quick answers

**Is CVE-2026-111902 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111902 being exploited in the wild.

**How severe is CVE-2026-111902?** Medium severity, with a CVSS score of 5.3, published 17 October 2026.

**Which products and versions are affected?** Thorsten phpMyFAQ 4.2.0-alpha through 4.2.0-alpha.2.

**Is there a fix for CVE-2026-111902?** Yes: fixed in 4.2.0-beta. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-111902 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-111902?** Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 4.2.0-beta

## Technical details

The isFaqAccessibleForUser() function in the public API endpoints (comments and attachments) uses a flawed logic: it returns true if either the FAQ has no translation for the requested language OR if the FAQ is actually visible to the user. When language detection is enabled (default), a mismatched Accept-Language header causes hasTranslation() to return false, short-circuiting the disjunction and bypassing the published/ACL/date-window checks. The frontend controllers use the correct isFaqRecordVisible() function and are not vulnerable.

## Affected products

- thorsten phpMyFAQ 4.2.0-alpha through 4.2.0-alpha.2

## Timeline

- 2026-10-03: disclosed
- 2026-10-17: advisory

## References

- [https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-g6fj-8cjr-wrxv](https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-g6fj-8cjr-wrxv)
- [https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha-before-4.2.0-beta-authorization-bypass-via-comments-and-attachments-api](https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha-before-4.2.0-beta-authorization-bypass-via-comments-and-attachments-api)

## Related threats

- [phpMyFAQ insufficient authorization in group deletion](https://junglewise.ai/threats/cve-2026-124433-phpmyfaq-before-4-1-11-contains-an-insufficient-authorization)
- [phpMyFAQ WebAuthn account enumeration in prepare-login](https://junglewise.ai/threats/cve-2026-124432-phpmyfaq-4-1-9-before-4-1-11-and-4-2-0-pre-releases-before-4-2-0)
- [phpMyFAQ authorization bypass in attachment downloads](https://junglewise.ai/threats/cve-2026-111910-phpmyfaq-before-4-1-9-and-4-2-0-alpha-before-4-2-0-beta-contains)
- [phpMyFAQ missing authorization in deleteUser API](https://junglewise.ai/threats/cve-2026-111909-phpmyfaq-before-4-1-9-contains-a-missing-authorization)
- [phpMyFAQ broken object-level authorization in FAQ update API](https://junglewise.ai/threats/cve-2026-111908-phpmyfaq-4-0-0-before-4-1-9-and-4-2-0-alpha-before-4-2-0-beta)