phpMyFAQ before 4.1.8 Authentication Bypass via Two-Factor Disable

Description

phpMyFAQ before 4.1.8 contains an authentication bypass vulnerability in its two-factor authentication (TOTP) disable functionality. The removeTwofactorConfig() handler (reachable via POST /api/user/remove-twofactor) verifies only that the user is logged in and that a valid CSRF token is supplied, then disables TOTP without requiring password re-entry or a current TOTP code. The same downgrade is also reachable inline via PUT /api/user/data/update, which accepts a plain twofactor_enabled form field under the same session+CSRF-only guard. An attacker who has hijacked a user's session can silently strip two-factor protection from any account, including administrator accounts, after which password-only authentication succeeds.

Scores

EPSS (exploitation in 30 days)

0.52% · top 56% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: poc · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Weakness

• CWE-308: Use of Single-factor Authentication (opens in a new tab)All about CWE-308 and its CVEs

Affected products

• thorsten · phpMyFAQ

  • affected < 4.1.8
  • unaffected 4.1.8

References (2)

• GitHub Security Advisory (GHSA-h96g-59xp-7r5m) (opens in a new tab)vendor-advisoryexploit
• VulnCheck Advisory: phpMyFAQ before 4.1.8 Authentication Bypass via Two-Factor Disable (opens in a new tab)third-party-advisory

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-85590](https://trackcve.app/badge/CVE-2026-85590.svg)](https://trackcve.app/cve/CVE-2026-85590)

Record last updated 4 Sept 2026, 14:01 UTC.