Technical impact
phpMyFAQ 4.1.9 through 4.1.11 and the alpha 4.2.0 releases before RC.2 contain a missing authentication flaw that permits an attacker who already holds a hijacked session to enroll passkeys using only the session and a WebAuthn CSRF token. By invoking the /api/webauthn/prepare and /api/webauthn/register endpoints, the attacker can replace the legitimate user’s passkeys, establishing a persistent passwordless login that survives any password changes or resets.
Affected Systems
Versions of phpMyFAQ from 4.1.9 up to (but not including) 4.1.12, as well as the alpha 4.2.0 series before RC.2, are affected. The vulnerability is present in each build of those releases that has not incorporated the fix found in phpMyFAQ 4.1.12 or 4.2.0-RC.2.
Risk and Exploitability
The CVSS score of 2.3 indicates a low overall severity, and the EPSS score is not available, suggesting no current widespread exploitation. However, the vulnerability requires an attacker to have a hijacked session, which is itself a significant condition. If an attacker succeeds in hijacking a session, they can bypass any single-factor authentication to enroll malicious passkeys, yielding persistent unauthorized access. The vulnerability is not listed in CISA’s KEV catalog, but the potential impact on account integrity warrants prompt remediation.