Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Information Scans·Updated Nov 19, 2026

CVE-2026-130352 Scanner

CVE-2026-130352 Scanner - Information Disclosure vulnerability in phpMyFAQ

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
6.9
CVSSmedium
Exploitable remotely over the internet · no authentication required.
Description

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
phpMyFAQby thorsten
AFFECTED< 4.1.12→SAFE ✓≥ 4.1.12
Updated Nov 19, 2026View on NVD →
Detail

phpMyFAQ is a popular open-source FAQ management application utilized by various organizations to provide structured and accessible solutions to common queries. Developed primarily for knowledge management, it is used by IT departments, customer service teams, and public information providers to improve information retrieval efficiency. The software supports multiple categories and languages, enhancing global compatibility for enterprises of all sizes. Its user-friendly interface and support for multimedia content make it a versatile choice for creating comprehensive FAQ repositories. Administrators primarily use phpMyFAQ to manage FAQ content, control access permissions, and generate insightful analytics on user interactions. The platform continuously receives feature updates and security patches to remain robust against evolving threats.

The Information Disclosure vulnerability in phpMyFAQ occurs due to improper access control within the FAQ list API. This vulnerability allows unauthorized attackers to read editor-only private notes by querying specific endpoints. Such endpoints include `/api/v4.0/faqs` and `/api/v3.1/faqs`, which inadvertently expose sensitive data meant for editors. This flaw potentially leads to unauthorized data exposure, compromising the confidentiality of internal communications. Attackers focusing on gathering sensitive organizational details can leverage this vulnerability for nefarious purposes. Consistent application of security best practices and vigilance is required to protect information confidentiality.

Technical exploitation of this vulnerability involves issuing unauthorized requests to API endpoints intended for internal use. Vulnerable versions of phpMyFAQ allow retrieval of sensitive information like private notes by manipulating API paths: `/api/v4.0/faqs` and `/api/v3.1/faqs`. The attacker can conduct this exploitation remotely due to insufficient restriction checks on these paths. Successful exploitation can result in critical exposure of internal remarks, which may contain sensitive operational or strategic information. Analyzing such traffic attempts is crucial for administrators to detect and defend against active exploitation.

Potential impacts of successful exploitation of this vulnerability include unauthorized access to confidential notes and operational details. This exposure can lead to reputational damage and competitive disadvantage by revealing strategic insights. Attackers may use exposed information for further targeted attacks, increasing organization vulnerability. Confidentiality breaches may also result in regulatory penalties if sensitive user data is disclosed. Mitigation requires urgent revision of access control mechanisms to comply with security best practices, thus enhancing overall resilience.

REFERENCES

Solution Advice
  • Update to phpMyFAQ version 4.1.12 or 4.2.0-RC.2 or later to patch the vulnerability.
  • Implement strict access control measures on all API endpoints to ensure only authorized users can access sensitive information.
  • Regularly audit and update API security configurations to detect and remediate vulnerabilities promptly.
  • Educate all editors and administrative users on securely managing access permissions to avoid inadvertent data disclosures.
  • Deploy network monitoring solutions to detect and respond to suspicious activities exploit reveals.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.