CVE-2026-76215
Received Received - Intake

phpMyFAQ Information Disclosure via API Endpoints

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: VulnCheck

Description
phpMyFAQ before 4.1.7 fails to apply parent FAQ visibility checks before returning child resources including comments and attachments. Unauthenticated attackers can retrieve restricted comment text, commenter email addresses, and attachment filenames for FAQ records they cannot directly access by querying the comments and attachments API endpoints.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-19
Last Modified
2026-08-19
Generated
2026-08-19
AI Q&A
2026-08-19
EPSS Evaluated
N/A
NVD
CVE-2026-76215
EUVD
EUVD-2026-62456

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.7 (exc)
phpmyfaq phpmyfaq 4.1.6

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

phpMyFAQ before version 4.1.7 has an authorization bypass where parent FAQ visibility checks are not applied before returning child resources like comments and attachments. Unauthenticated attackers can access restricted data by querying specific API endpoints, such as retrieving comment text, email addresses, and attachment filenames for FAQ records they cannot view.

Detection Guidance

To detect this vulnerability, check if unauthorized users can access restricted comments or attachments via API endpoints. Test GET requests to /api/v3.1/comments/{recordId} and /api/v3.1/attachments/{recordId} for non-public FAQ records. If sensitive data like emails or filenames is returned, the system is vulnerable.

Impact Analysis

This vulnerability allows attackers to access sensitive information such as comment content, email addresses of commenters, and attachment filenames for restricted FAQ records. Attackers can enumerate FAQ IDs and retrieve data without authentication, potentially exposing personally identifiable information (PII) and business-sensitive details.

Compliance Impact

This vulnerability may violate compliance with GDPR and HIPAA due to unauthorized access to personally identifiable information (PII) such as email addresses and comment content. Exposure of such data could result in legal penalties, data breach notifications, and reputational damage for organizations using affected phpMyFAQ versions.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.1.7 or later to apply the missing authorization checks. If immediate upgrade is not possible, restrict access to the /api/v3.1/comments and /api/v3.1/attachments endpoints via firewall rules or disable them temporarily.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-76215. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart