CVE-2026-111884
phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta does not require the current password when…
- Risk score
- 55/100
- CVSS
- 8.3 v3.1
- Exploit chance (30 days)
- 0.3%
- Published
- 17 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 mailb…
- Affected
- See advisory
- Fix
- Upgrade the product to 4.1.9 or 4.2.0 (whichever matches your release line), or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 8.3 high
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-7554-gx6g-xx77
- https://www.vulncheck.com/advisories/phpmyfaq-before-4.1.9-and-4.2.0-alpha-before-4.2.0-beta-missing-current-password-step-up-on-e-mail-change-enables-account-takeover
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-7554-gx6g-xx77
Original 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.
Last activity 17 Oct 2026. Patch Forecast updates every hour.