Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111904 Overview
CVE-2026-111904 is an information disclosure vulnerability in phpMyFAQ 4.2.0-alpha before 4.2.0-beta. The flaw resides in the OpenQuestionController, where an inverted api.onlyPublicQuestions check causes the application to return non-public questions instead of filtering them out. Unauthenticated attackers can send GET requests to the /api/v4.0/open-questions endpoint to read hidden moderation or internal questions along with the usernames tied to them. The weakness is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Critical Impact
Unauthenticated remote attackers can retrieve hidden open questions and associated usernames from affected phpMyFAQ deployments, exposing moderation content and user identity data.
Affected Products
- phpMyFAQ 4.2.0-alpha
- All releases between 4.2.0-alpha and 4.2.0-beta
- Deployments exposing the /api/v4.0/open-questions endpoint
Discovery Timeline
- 2026-10-17 - CVE-2026-111904 published to NVD
- 2026-10-18 - Last updated in NVD database
Technical Details for CVE-2026-111904
Vulnerability Analysis
phpMyFAQ exposes an open-questions API that is designed to return only questions explicitly marked as public. The OpenQuestionController enforces this restriction through a configuration flag named api.onlyPublicQuestions. In the vulnerable 4.2.0-alpha branch, the conditional logic evaluating this flag is inverted. When administrators enable the setting to restrict output to public items, the controller instead returns the non-public set.
The response payload includes the question text and the username associated with each submission. Attackers can therefore enumerate pending moderation queues and internal discussions without authenticating. The endpoint responds to simple GET requests, which lowers the technical barrier for exploitation and enables automated scraping.
Root Cause
The root cause is a logic error in the authorization filter inside OpenQuestionController. The boolean check that gates access to non-public questions evaluates to the opposite of its intended state. This bypasses the privacy control that administrators rely on to hide moderation items from anonymous visitors. The fix in 4.2.0-beta restores the correct evaluation of the api.onlyPublicQuestions configuration.
Attack Vector
Exploitation requires network access to the phpMyFAQ instance and no credentials or user interaction. An attacker issues an HTTP GET request to /api/v4.0/open-questions. The vulnerable controller returns a JSON structure containing hidden questions and the usernames tied to them. Attackers can replay the request on a schedule to harvest newly submitted internal content.
See the GitHub Security Advisory GHSA-6xm9-p734-8fx6 and the VulnCheck Advisory for phpMyFAQ 4.2.0 for additional technical context.
Detection Methods for CVE-2026-111904
Indicators of Compromise
- Unauthenticated HTTP GET requests to /api/v4.0/open-questions from external IP addresses
- Repeated or sequential polling of the open-questions endpoint from a single source
- Unexpected spikes in outbound JSON response size from the phpMyFAQ web server
- Web server access logs showing anonymous sessions reading moderation data
Detection Strategies
- Review web access logs for GET requests to /api/v4.0/open-questions without an authenticated session cookie or API token.
- Correlate response size and status codes to identify successful disclosure responses versus empty results.
- Compare the running phpMyFAQ version against the fixed 4.2.0-beta release using asset inventory data.
Monitoring Recommendations
- Enable verbose logging on the phpMyFAQ API routes and forward the logs to a centralized SIEM for correlation.
- Alert on anonymous access to any /api/v4.0/ endpoint that is expected to return filtered content.
- Track user-agent diversity against the open-questions endpoint to spot automated scraping behavior.
How to Mitigate CVE-2026-111904
Immediate Actions Required
- Upgrade phpMyFAQ to version 4.2.0-beta or later, which contains the corrected api.onlyPublicQuestions check.
- Audit historical access logs for prior GET requests to /api/v4.0/open-questions and identify any data that may have been disclosed.
- Notify users whose submissions were marked non-public that their questions and usernames may have been exposed.
Patch Information
The maintainers resolved the inverted conditional in OpenQuestionController in phpMyFAQ 4.2.0-beta. Administrators running any 4.2.0-alpha build should upgrade immediately. Refer to the GitHub Security Advisory GHSA-6xm9-p734-8fx6 for release details.
Workarounds
- Block unauthenticated external access to /api/v4.0/open-questions at the reverse proxy or web application firewall layer until the patch is applied.
- Restrict the phpMyFAQ administration and API surface to trusted IP ranges using network ACLs.
- Temporarily disable the open-questions feature if the API is not required for production use.
# Example nginx block for the vulnerable endpoint
location = /api/v4.0/open-questions {
allow 10.0.0.0/8;
deny all;
return 403;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

