Skip to main content
VulnerabilityPublished Updated

CVE-2026-75918: thorsten phpMyFAQ · Information Exposure

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 8.7 High : upgrade to 4.1.7 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade phpMyFAQ and thorsten/phpMyFAQ to 4.1.7.

Affected software

ProductAffectedFixed in
thorstenphpMyFAQAffected
  • <4.1.7
Fixed in
  • 4.1.7
GitHubthorsten/phpMyFAQpkg:github/thorsten/phpMyFAQOther threatsAffected
  • <4.1.7
Fixed in
  • 4.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…