thorsten phpMyFAQ up to 4.0.12 User Registration incorrect user management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in thorsten phpMyFAQ up to 4.0.12. This impacts an unknown function of the component User Registration Handler. Such manipulation leads to incorrect user management. This vulnerability is traded as CVE-2025-59943. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in thorsten phpMyFAQ up to 4.0.12 and classified as critical. Affected by this issue is an unknown function of the component User Registration Handler. The manipulation with an unknown input leads to a incorrect user management vulnerability. Using CWE to declare the problem leads to CWE-286. The product does not properly manage a user within its environment. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-59943 since 09/23/2025. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 4.0.13 eliminates this vulnerability. Applying the patch 44cd20f86eb041f39d1c30a9beefad1cc61dc0ec is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrect user managementCWE: CWE-286
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: phpMyFAQ 4.0.13
Patch: 44cd20f86eb041f39d1c30a9beefad1cc61dc0ec
Timeline
09/23/2025 CVE reserved10/04/2025 Advisory disclosed
10/04/2025 VulDB entry created
10/11/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-9wj2-4hcm-r74j
Status: Confirmed
CVE: CVE-2025-59943 (🔒)
GCVE (CVE): GCVE-0-2025-59943
GCVE (VulDB): GCVE-100-326984
Entry
Created: 10/04/2025 07:50Updated: 10/11/2025 04:13
Changes: 10/04/2025 07:50 (67), 10/11/2025 04:13 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.