Quick answers
- Is CVE-2026-85590 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85590 being exploited in the wild.
- How severe is CVE-2026-85590?
- Informational severity, with a CVSS score of 7.1, published 4 September 2026.
- Which products and versions are affected?
- Thorsten phpMyFAQ before 4.1.8.
- Is there a fix for CVE-2026-85590?
- A patch was published on 2026-09-04: Patched in version 4.1.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85590 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-85590?
- Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass in the two-factor authentication disable functionality, rooted in CWE-308 (Use of Single-factor Authentication). The removeTwofactorConfig() API endpoint (POST /api/user/remove-twofactor) and the inline twofactor_enabled form field in PUT /api/user/data/update both check only for an active session and valid CSRF token—they do not require password re-entry, current TOTP code, or any step-up authentication. An attacker with session hijacking (e.g., via XSS or session theft) can send a single request with a harvested CSRF token to strip 2FA protection from any account. The vulnerability affects phpMyFAQ versions before 4.1.8 and has been patched in version 4.1.8. Attack vector is network-based with low complexity and requires only low privileges (an authenticated session).
Affected products
- thorsten phpMyFAQ before 4.1.8
Timeline
- 2026-08-20: disclosed: Vulnerability reported via GitHub Security Advisory
- 2026-09-04: advisory: Public disclosure and CVE publication
- 2026-09-04: patched: Patched in version 4.1.8