CVE•Published 2026-08-19•Modified 2026-09-01•1 article on news•5 live references•NVD data
CVE-2026-75918Phpmyfaq · Phpmyfaq
Vulnerability data via NVD (ingested)
CVSS v3.1
8.8
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS percentile
17
Exploit Prediction Scoring System · top 83% of all CVEs
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.
Timeline
Published 2026-08-19
Modified 2026-09-01
External references
Search for exposed instances
Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).
Shodan · vuln tag0 hosts
vuln:CVE-2026-75918Hosts Shodan has explicitly fingerprinted as vulnerable.
Shodan · product
product:"Phpmyfaq Phpmyfaq"All exposed Phpmyfaq Phpmyfaq instances — cross-reference with the CVE's affected-version range.
Shodan · banner/body mention
http.html:"Phpmyfaq"HTTP body or banner mentions "Phpmyfaq" — catches deploys Shodan didn't identify as a product.
More intel sources (5)
Shodan report
vuln:CVE-2026-75918Country / ASN / product breakdown for the vuln query.
Censys
vulnerabilities.cve_id: CVE-2026-75918Censys host search filtered to this CVE id.
grep.app
CVE-2026-75918Public source-code mentions — fast PoC discovery.
GitHub code
CVE-2026-75918GitHub code search for direct mentions.
Google dork
"CVE-2026-75918" exploit -site:nvd.nist.govWrite-ups and news, NVD excluded.
Known PoCs on GitHub
No public proof-of-concept repositories found for CVE-2026-75918 on GitHub.