Skip to main content
EPSS 0.5%top 60%

CVE-2026-75918: Exposure of Sensitive Information to an Unauthorized Actor in thorsten phpMyFAQ

0
High
Published: 08/19/2026 (08/19/2026, 14:01:51 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ versions before 4.1.7 have a vulnerability where password reset tokens are stored in a publicly accessible tracking file if user tracking is enabled. This allows unauthenticated attackers to read these tokens and use them to reset passwords, potentially taking over user accounts.

CVSS v4.0

Score 8.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected software

thorsten

phpMyFAQ

Affected versions
>=0 <4.1.7
GitHub Actionsmore threats →ai
thorsten/phpMyFAQ
pkg:github/thorsten/phpMyFAQ
Affected versions
<4.1.7

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/11/2026, 08:49:39 UTC

Technical Analysis

In phpMyFAQ versions prior to 4.1.7, when user tracking is enabled, password reset tokens are stored insecurely in a publicly accessible file located at content/core/data/trackingDDMMYYYY. Because this file is accessible without authentication, attackers can retrieve reset tokens and replay them against the password reset API to hijack user accounts. This vulnerability is identified as CVE-2026-75918 and has a CVSS 4.0 score of 8.7, indicating high severity.

Potential Impact

An unauthenticated attacker can access password reset tokens by reading a publicly accessible tracking file and then use these tokens to reset passwords and take over user accounts. This compromises user account confidentiality and integrity.

Mitigation Recommendations

Upgrade phpMyFAQ to version 4.1.7 or later, where this vulnerability is fixed. Until then, consider disabling user tracking to prevent the storage of reset tokens in publicly accessible files. Patch status is confirmed by the version boundary; versions before 4.1.7 are affected, so updating to 4.1.7 or later mitigates the issue.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-08-18T15:05:54.226Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a85bc6bacd9273b492f486a

Added to database: 08/19/2026, 14:23:39 UTC

Last enriched: 09/11/2026, 08:49:39 UTC

Last updated: 10/04/2026, 10:02:29 UTC

Views: 53

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses