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.
Published: 2026-09-04
Score: 7.1 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an attacker who has hijacked a user session to disable two‑factor authentication by calling the remove-twofactor endpoint or by updating the twofactor_enabled field via the data update API. The request only requires a logged‑in user session and a valid CSRF token, without requiring the current password or a TOTP code. Once two‑factor is disabled, the account—including administrator accounts—can be accessed with only a password, effectively bypassing strong authentication. This flaw is a classic authentication bypass (CWE‑308).

Affected Systems

The issue affects the phpMyFAQ application from the vendor thorsten. Versions prior to 4.1.8 are vulnerable; use phpMyFAQ 4.1.8 or later to eliminate the flaw.

Risk and Exploitability

The CVSS score of 7.1 indicates moderate to high severity. The EPSS score is unavailable, and the vulnerability is not listed in the CISA KEV catalog. An attacker with a hijacked session token can exploit the flaw via remote web requests, leading to privilege revocation of two‑factor protection. Because the bypass requires only the standard session cookies and a valid CSRF token, there is a practical risk of exploitation when session hijacking or cross‑site request forgery defenses are weak.

Generated by OpenCVE AI on September 4, 2026 at 12:28 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update phpMyFAQ to version 4.1.8 or newer.
  • Restrict or remove the remove-twofactor and data update endpoints from the API or enforce password re‑entry before disabling two‑factor authentication.
  • Audit the application to ensure that session management, CSRF protection, and two‑factor configuration changes are properly secured and monitored for suspicious activity.

Generated by OpenCVE AI on September 4, 2026 at 12:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 11:45:00 +0000

Type Values Removed Values Added
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.
Title phpMyFAQ before 4.1.8 Authentication Bypass via Two-Factor Disable
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-308
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Phpmyfaq Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-04T11:29:56.063Z

Reserved: 2026-09-04T10:59:00.162Z

Link: CVE-2026-85590

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T12:17:21.327

Modified: 2026-09-04T12:17:21.327

Link: CVE-2026-85590

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T12:30:17Z

Weaknesses
  • CWE-308

    Use of Single-factor Authentication