GHSA-7582-hcc6-fvcg
phpMyFAQ versions before 4.1.5 have inconsistent filtering on their public FAQ API endpoints, which allows unauthenticated attackers to access inactive FAQ content such as drafts or review-only entries. Some API endpoints return full inactive FAQ answers, while others return titles and answer previews, exposing non-public information.
AI Analysis
Technical Summary
The vulnerability in phpMyFAQ prior to version 4.1.5 involves inconsistent application of active=yes and publication-date filters across multiple public FAQ API endpoints. This inconsistency permits unauthenticated users to retrieve inactive FAQ content. Specifically, the GET /api/v3.1/faq/{categoryId}/{faqId} endpoint discloses the inactive FAQ title and full answer, whereas the GET /api/v3.1/faqs/tags/{tagId} and GET /api/v4.0/faqs/tags/{tagId} endpoints reveal the inactive FAQ title and an answer preview. This results in unauthorized disclosure of draft or review-only FAQ content.
Potential Impact
Unauthenticated attackers can access inactive FAQ content that is intended to remain private, including draft or review-only entries. This leads to unauthorized information disclosure, potentially exposing sensitive or internal information that could aid further attacks or cause reputational damage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects phpMyFAQ versions before 4.1.5, upgrading to version 4.1.5 or later is recommended once a fix is available. Until then, restrict access to the affected API endpoints or implement additional access controls to prevent unauthorized retrieval of inactive FAQ content.
GHSA-7582-hcc6-fvcg
Description
phpMyFAQ versions before 4.1.5 have inconsistent filtering on their public FAQ API endpoints, which allows unauthenticated attackers to access inactive FAQ content such as drafts or review-only entries. Some API endpoints return full inactive FAQ answers, while others return titles and answer previews, exposing non-public information.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in phpMyFAQ prior to version 4.1.5 involves inconsistent application of active=yes and publication-date filters across multiple public FAQ API endpoints. This inconsistency permits unauthenticated users to retrieve inactive FAQ content. Specifically, the GET /api/v3.1/faq/{categoryId}/{faqId} endpoint discloses the inactive FAQ title and full answer, whereas the GET /api/v3.1/faqs/tags/{tagId} and GET /api/v4.0/faqs/tags/{tagId} endpoints reveal the inactive FAQ title and an answer preview. This results in unauthorized disclosure of draft or review-only FAQ content.
Potential Impact
Unauthenticated attackers can access inactive FAQ content that is intended to remain private, including draft or review-only entries. This leads to unauthorized information disclosure, potentially exposing sensitive or internal information that could aid further attacks or cause reputational damage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects phpMyFAQ versions before 4.1.5, upgrading to version 4.1.5 or later is recommended once a fix is available. Until then, restrict access to the affected API endpoints or implement additional access controls to prevent unauthorized retrieval of inactive FAQ content.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7582-hcc6-fvcg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-57994"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a520eea68715ace4391d4b3
Added to database: 07/11/2026, 09:37:46 UTC
Last enriched: 07/11/2026, 10:08:44 UTC
Last updated: 07/12/2026, 03:33:47 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.