Account ambiguity via unchecked duplicate email registration
Published Oct 3, 2025 · Updated Oct 3, 2025
Incorrect user management in phpMyFAQ 4.0.7 through 4.0.12 allows remote attackers to create multiple accounts with one email. RegistrationHelper::createUser and User::createUser inserted account data without checking whether faquserdata already contained the submitted email. Registration is unauthenticated; account takeover or privilege escalation additionally requires an email-based reset or administrative flow to select the wrong account.
Summary
What happened
Incorrect user management in phpMyFAQ 4.0.7 through 4.0.12 allows remote attackers to create multiple accounts with one email. RegistrationHelper::createUser and User::createUser inserted account data without checking whether faquserdata already contained the submitted email. Registration is unauthenticated; account takeover or privilege escalation additionally requires an email-based reset or administrative flow to select the wrong account.
The record
- CVE
- CVE-2025-59943
- Published
- Oct 3, 2025
- Updated
- Oct 3, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-286, CWE-284, T1136
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 3, 2025CVE publishedPublication date reported by the CVE source.
- Oct 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.0.7, < 4.0.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor duplicate-registration reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo