phpMyFAQ: Use of Single-factor Authentication
CVE-2026-111884 is a high-severity use of single-factor authentication vulnerability in phpMyFAQ from Thorsten, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 4.1.9, 4.2.0-beta as the first without the flaw, so updating phpMyFAQ to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.35% 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.9 or 4.2.0-beta, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Thorsten | phpMyFAQ | before 4.1.9; 4.2.0-alpha up to, but not including, 4.2.0-beta | 4.1.9, 4.2.0-beta |
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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 8.3 | High | CNA (vulncheck.com) |
Official description
phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta does not require the current password when changing an account e-mail in the user control panel (UserController::updateData, api/user/data/update), checking only the session and CSRF token. An attacker with a hijacked session can set the e-mail to their own mailbox and use the password-reset flow to take over non-2FA accounts, including superadmin.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Single-factor Authentication
The product uses an authentication algorithm that uses a single factor (e.g., a password) in a security context that should require more than one factor.
How developers prevent this class of flaw
- Use multiple independent authentication schemes, which ensures that -- if one of the methods is compromised -- the system itself is still likely safe from compromise. For this reason, if multiple schemes are possible, they should be implemented and required -- especially if they are easy to use.
More Use of Single-factor Authentication vulnerabilities (CWE-308)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- 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 Use of Single-factor Authentication vulnerabilities
- 8.1 High severity
- 9.8 Critical severity
- 7.1 High severity
- 8.1 High severity
- 9.1 Critical severity
- 8.1 High severity
Spotted an error? Tell us.