Skip to main content
CVE-2025-59943VulnerabilityPublished

CVE-2025-59943: thorsten phpMyFAQ · Incorrect User Management

Affects thorsten phpMyFAQSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High · fixed in 4.0.13 : patch thorsten phpMyFAQ soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. 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 2026-10-26.

What to do

AI-suggested

European organizations should immediately upgrade phpMyFAQ installations to version 4.0.13 or later, where the vulnerability is fixed by enforcing unique email addresses during user registration. Until the upgrade can be performed, organizations should implement compensating controls such as: 1) Enhancing password reset workflows to require additional verification beyond email ownership, such as multi-factor authentication or security questions. 2) Monitoring user registration logs for multiple accounts sharing the same email and manually reviewing or disabling suspicious accounts. 3) Restricting administrative actions and notifications to verified accounts with unique identifiers. 4) Implementing application-layer filters or custom patches to enforce email uniqueness if upgrading is delayed. 5) Educating users and administrators about the risks of shared email accounts and encouraging use of unique email addresses. Additionally, organizations should audit their phpMyFAQ configurations to ensure that email-based processes do not rely solely on the email address as a unique identifier and consider integrating stronger identity verification mechanisms. Regular security assessments and monitoring for anomalous account activities related to email reuse are also recommended.

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.

References

Community reviews

Loading reviews…