CVE-2026-130370

phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Passkey Enrollment Missing Step-Up Authentication

Published Nov 17, 2026 CVSS 4.0 · 2.3 Low EPSS n/a KEV · Not listed
Description
phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authentication vulnerability that allows attackers holding a hijacked session to enroll passkeys using only the session and webauthn CSRF token. Attackers can call /api/webauthn/prepare and /api/webauthn/register to replace the owner's passkeys, gaining persistent passwordless login that survives password changes and resets.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.12 or later or to 4.2.0-RC.2 or later to apply the vendor’s fix.
  • Ensure session management is hardened so that hijacked sessions cannot be reused, such as by rotating session identifiers on authentication and enforcing strict cookie attributes.
  • If an immediate upgrade is not possible, restrict access to the /api/webauthn/prepare and /api/webauthn/register endpoints to trusted roles or temporarily disable passkey enrollment until a patch can be applied.

Generated by OpenCVE AI on November 17, 2026 at 02:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authentication vulnerability that allows attackers holding a hijacked session to enroll passkeys using only the session and webauthn CSRF token. Attackers can call /api/webauthn/prepare and /api/webauthn/register to replace the owner's passkeys, gaining persistent passwordless login that survives password changes and resets.
Title phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Passkey Enrollment Missing Step-Up Authentication
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-306
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 4.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

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

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 17, 2026, 1:40 AM
Reserved
Nov 17, 2026, 1:06 AM
Status
Deferred
Published
Nov 17, 2026, 2:17 AM
Modified
Nov 17, 2026, 2:17 AM