CVE-2025-59943

phpMyFAQ does 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.

Details

An account management logic flaw in phpMyFAQ allows attackers to register multiple accounts under the same email address. If email is used for password reset or administrative flows, this may result in account takeover, loss of accountability, and abuse of business logic.

PoC

1.Register a user with email [email protected]
2.Register another user with the same email.
3.Both accounts appear in /admin/?action=user&user_action=listallusers.

-Data integrity loss: Multiple accounts mapped to one email break auditability.
-Password reset ambiguity: If reset flow relies on email only, attackers can target or take over accounts.
-Privilege escalation: If one account with the same email has admin privileges, an attacker controlling the email may escalate.
-Spam / DoS: Attackers can mass-register accounts with a single email to pollute the system.

This is a business logic / authentication vulnerability. Impacted users are anyone relying on phpMyFAQ’s account system where email is assumed to be unique.

CVE-2025-59943 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.13); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-59943? CVE-2025-59943 is a high-severity security vulnerability in thorsten/phpmyfaq (composer), affecting versions >= 4.0.7, < 4.0.13. It is fixed in 4.0.13.
2. How severe is CVE-2025-59943? CVE-2025-59943 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of thorsten/phpmyfaq are affected by CVE-2025-59943? thorsten/phpmyfaq (composer) versions >= 4.0.7, < 4.0.13 is affected.
4. Is there a fix for CVE-2025-59943? Yes. CVE-2025-59943 is fixed in 4.0.13. Upgrade to this version or later.
5. Is CVE-2025-59943 exploitable, and should I be worried? Whether CVE-2025-59943 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-59943 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-59943? Upgrade thorsten/phpmyfaq to 4.0.13 or later.