Unauthenticated inactive FAQ disclosure via omitted filters
Published Jul 10, 2026 · Updated Jul 10, 2026
Information disclosure in phpMyFAQ 4.1.0 through 4.1.4 allows remote attackers to retrieve inactive FAQ content through public APIs. Faq::getFaqsByIds() and Faq::getFaqByIdAndCategoryId() omit active-status and publication-window filters while returning titles, previews, or full answers. Exploitation requires public API access and an inactive FAQ that is anonymously readable, limiting the result to disclosure of that content.
Summary
What happened
Information disclosure in phpMyFAQ 4.1.0 through 4.1.4 allows remote attackers to retrieve inactive FAQ content through public APIs. Faq::getFaqsByIds() and Faq::getFaqByIdAndCategoryId() omit active-status and publication-window filters while returning titles, previews, or full answers. Exploitation requires public API access and an inactive FAQ that is anonymously readable, limiting the result to disclosure of that content.
The record
- CVE
- CVE-2026-57994
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-863, CWE-200, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 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.1.0 <4.1.5
What conditions does exploitation require?
What is affected?
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
- Inactive FAQ API exposure 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