CVE-2026-130352 in phpMyFAQ
Summary
by MITRE • 11/17/2026
phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows unauthenticated attackers to read editor-only Private Notes by querying the public FAQ list API. Attackers can page through GET /api/v4.0/faqs or /api/v3.1/faqs without credentials to retrieve the notes field of every anonymously readable FAQ, exposing internal remarks and ticket details.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/17/2026
The vulnerability identified in phpMyFAQ versions prior to 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 represents a critical failure in access control mechanisms within the application's public-facing API endpoints. This flaw allows unauthenticated attackers to bypass intended security restrictions by exploiting the FAQ list retrieval functions, specifically through GET requests directed at /api/v4.0/faqs or /api/v3.1/faqs. The core technical issue lies in the improper separation of privileges between anonymous users and authenticated editors. While the application correctly restricts access to private notes for most operations, it fails to filter out sensitive fields when generating public lists of frequently asked questions. Consequently, any user with network connectivity to the server can iterate through available FAQs without providing valid credentials or session tokens.
From a technical perspective, this vulnerability is classified under CWE-200: Information Exposure and more specifically aligns with CWE-862: Missing Authorization. The application logic retrieves FAQ records for display purposes but inadvertently includes the notes field in the JSON response payload even when the requesting user lacks the necessary permissions to view private editor comments or internal ticket details. This behavior violates the principle of least privilege, as data intended solely for administrative review is exposed through a public interface designed for general audience consumption. The attacker can programmatically page through these endpoints using standard HTTP methods, extracting structured data that contains confidential operational information.
The operational impact of this vulnerability extends beyond simple data leakage. Private notes in phpMyFAQ often contain sensitive internal remarks, troubleshooting steps not meant for external publication, and details regarding support ticket resolutions. Exposure of such information can lead to significant reputational damage if proprietary processes or customer-specific issues are revealed publicly. Furthermore, the disclosed information may serve as reconnaissance material for subsequent attacks. Knowledge of internal workflows, known bugs, or pending fixes can aid attackers in crafting more targeted exploits against other components of the system or related infrastructure. This aligns with ATT&CK technique T1087: Account Discovery and potentially T1530: Data from Cloud Storage Object APIs if the data is considered part of a broader information gathering campaign.
Mitigation strategies must focus on immediate patching and enhanced access control validation. Administrators should upgrade phpMyFAQ to version 4.1.12 or later, where this authorization check has been corrected to ensure that private notes are excluded from public API responses unless the requester possesses appropriate editor privileges. In addition to upgrading, organizations should implement strict input validation and output encoding on all API endpoints to prevent unintended data leakage. It is also advisable to review other API versions for similar inconsistencies in field filtering logic. Security monitoring tools should be configured to detect unusual patterns of automated requests against FAQ listing endpoints, which may indicate active exploitation attempts by malicious actors seeking to harvest sensitive internal documentation.