CVE-2026-111886

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-beta lacks brute-force lockout in the removeTwofactorConfig 2FA removal endpoint, allowing authenticated attackers to guess TOTP codes without limit. Attackers holding a hijacked session and CSRF token can repeatedly POST guesses to...

EUVD-2026-103333

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-beta lacks brute-force lockout in the removeTwofactorConfig 2FA removal endpoint, allowing authenticated attackers to guess TOTP codes without limit. Attackers holding a hijacked session and CSRF token can repeatedly POST guesses to...

PT-2026-116457

Name of the Vulnerable Software and Affected Versions phpMyFAQ versions 4.2.0-alpha.2 through 4.2.0-beta Description The software lacks a brute-force lockout mechanism in the removeTwofactorConfig function. This allows authenticated attackers who possess a hijacked session and a CSRF token to...

phpMyFAQ removeTwofactorConfig Bypass

The vulnerability of the removeTwofactorConfig function in the phpMyFAQ web application is related to the lack of authentication for the critical function. Exploiting this vulnerability could allow a malicious actor to bypass existing security measures remotely...

Use of Single-factor Authentication

Overview phpmyfaq/phpmyfaq is a FAQ system for PHP and MySQL, PostgreSQL and other databases Affected versions of this package are vulnerable to Use of Single-factor Authentication through the removeTwofactorConfig process and the twofactorenabled form field, which are accessible via POST...

CVE-2026-85590: Use of Single-factor Authentication

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...