Unauthenticated data disclosure via unfiltered API responses
Published Jan 24, 2026 · Updated Jan 24, 2026
Information disclosure in phpMyFAQ before 4.0.17 allows remote attackers to read email addresses and non-public content via public APIs. OpenQuestionController::list() passes showAll=true to Question::getAll(), placing invisible questions and submitter emails in responses; comment, news, and FAQ APIs have similar missing filters. No account or user interaction is required, and disclosure is limited to data returned by the affected endpoints.
Summary
What happened
Information disclosure in phpMyFAQ before 4.0.17 allows remote attackers to read email addresses and non-public content via public APIs. OpenQuestionController::list() passes showAll=true to Question::getAll(), placing invisible questions and submitter emails in responses; comment, news, and FAQ APIs have similar missing filters. No account or user interaction is required, and disclosure is limited to data returned by the affected endpoints.
The record
- CVE
- CVE-2026-24422
- Published
- Jan 24, 2026
- Updated
- Jan 24, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2026CVE publishedPublication date reported by the CVE source.
- Jan 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.0.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Unauthenticated open-questions API curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo