Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Misconfiguration·Updated Nov 17, 2026

CVE-2026-75918 Scanner

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

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

phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and replay them against the password reset API to take over user accounts.

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

phpMyFAQ is widely used as a content management system for frequently asked questions. It's utilized by organizations to provide users with easy access to commonly sought information on various topics. Deployed on web servers, phpMyFAQ enables users to create, manage, and search FAQ entries effectively. System administrators primarily manage this software to keep FAQ content updated and relevant. It's extensively adopted due to its ease of use and adaptability in different industrial domains where knowledge sharing is crucial. Users appreciate its customizable features that cater to specific needs, enhancing public information accessibility.

The identified vulnerability allows unauthenticated attackers to exploit exposed password reset tokens in phpMyFAQ versions prior to 4.1.7. Password reset tokens are stored in a publicly accessible tracking file, permitting attackers to read and potentially manipulate this sensitive data. The exposure of these tokens poses significant security risks, particularly account takeover scenarios. Attackers need user tracking to be enabled to carry out this exploitation effectively. This oversight leads to a severe risk classification, emphasizing the urgency for users to update their systems promptly. Organizations utilizing vulnerable versions must prioritize upgrading to mitigate potential breaches.

Technically, the vulnerability exists due to improper storage of password reset tokens in tracking files that are accessible without authentication. The vulnerable endpoint allows unrestricted reads from these files, typically stored with inadequate access controls. Exploiting this vulnerability involves sending appropriate requests to the phpMyFAQ server, thereby retrieving potentially sensitive tokens. Attackers can replay these tokens to hijack user accounts under the assumption of legitimate recovery processes. The flaw resides in poor management of sensitive data, which should be internally secured and inaccessible to unauthorized entities. As a result, this weakness in the authentication process constitutes a critical threat vector.

Exploiting the vulnerability can lead to substantial concerns, primarily unauthorized access to user accounts. Malicious entities could exploit these reset tokens to bypass regular authentication mechanisms entirely. This breach potentially exposes private user data and administrative functionalities to attackers. Users might experience account lockouts or suspicious activity due to unauthorized privilege escalations. Financial losses and reputational damages are among the severe consequences for organizations failing to address this security concern. Prompt patching and strict data governance are essential to combatting such exploitations efficiently.

REFERENCES

Solution Advice
  • Update phpMyFAQ to version 4.1.7 or later to mitigate this vulnerability.
  • Ensure sensitive data such as password reset tokens are stored securely with restricted access permissions.
  • Disable user tracking if not required, to prevent unnecessary exposure of sensitive information.
  • Implement stricter authentication mechanisms to ensure only authorized users can access critical functions.
  • Regularly audit and monitor server configurations and files for unexpected exposure of sensitive information.

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.