phpMyFAQ: Weak Password Recovery Mechanism for Forgotten Password
CVE-2026-35676 is a high-severity weak password recovery mechanism for forgotten password vulnerability in phpMyFAQ from Thorsten, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.1.3 as the first without the flaw, so updating phpMyFAQ to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.3% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update phpMyFAQ to 4.1.3 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.8 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 8.2 | High | CNA (vulncheck.com) |
Official description
phpMyFAQ before 4.1.3 contains an unauthenticated password reset vulnerability in the user password update API endpoint that allows attackers to change account passwords without token validation. Attackers can enumerate valid username and email pairs and force immediate password changes by sending PUT requests to the /api/index.php/user/password/update endpoint, causing account disruption and invalidating legitimate user credentials.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Weak Password Recovery Mechanism for Forgotten Password
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
How developers prevent this class of flaw
- Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
- Do not use standard weak security questions and use several security questions.
- Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.
More Weak Password Recovery Mechanism for Forgotten Password vulnerabilities (CWE-640)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in phpMyFAQ
- 7.3 High severity
- 7.5 High severity
- 9.8 Critical severity
- 8.1 High severity
- 8.3 High severity
- 7.1 High severity
Recent Weak Password Recovery Mechanism for Forgotten Password vulnerabilities
- 8.8 High severity
- 8.1 High severity
- 8.1 High severity
- 7.4 High severity
- 9.8 Critical severity
- 7.1 High severity
Spotted an error? Tell us.