CVE•Published 2025-10-03•Modified 2026-10-08•1 article on news•6 live references•NVD data
CVE-2025-59943Phpmyfaq · Phpmyfaq
Vulnerability data via NVD (ingested)
CVSS v3.1
8.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS percentile
34
Exploit Prediction Scoring System · top 66% of all CVEs
Weaknesses (CWE)
Description
phpMyFAQ is an open source FAQ web application. Versions 4.0-nightly-2025-10-03 and below do not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause account ambiguity and, in certain configurations, may lead to privilege escalation or account takeover. This issue is fixed in version 4.0.13.
Timeline
Published 2025-10-03
Modified 2026-10-08
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-2025-59943Hosts Shodan has explicitly fingerprinted as vulnerable.
Shodan · product + version
product:"Phpmyfaq Phpmyfaq" version:"4.0.7"Version-pinned fingerprint from NVD's first vulnerable CPE.
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-2025-59943Country / ASN / product breakdown for the vuln query.
Censys
vulnerabilities.cve_id: CVE-2025-59943Censys host search filtered to this CVE id.
grep.app
CVE-2025-59943Public source-code mentions — fast PoC discovery.
GitHub code
CVE-2025-59943GitHub code search for direct mentions.
Google dork
"CVE-2025-59943" exploit -site:nvd.nist.govWrite-ups and news, NVD excluded.
Known PoCs on GitHub
No public proof-of-concept repositories found for CVE-2025-59943 on GitHub.