CVE-2026-130370
Deferred Deferred - Pending Action

Authentication Bypass via Passkey Hijacking in phpMyFAQ

Vulnerability report for CVE-2026-130370, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.12 (exc)
phpmyfaq phpmyfaq to 4.2.0-RC.2 (exc)
phpmyfaq phpmyfaq From 4.1.9 (inc) to 4.1.11 (inc)
phpmyfaq phpmyfaq From 4.2.0-alpha (inc) to 4.2.0-RC.2 (exc)
phpmyfaq phpmyfaq 4.1.12
phpmyfaq phpmyfaq 4.2.0-RC.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in phpMyFAQ versions 4.1.9 to 4.1.11 and 4.2.0-alpha to 4.2.0-RC.1 allows attackers with a hijacked session to enroll new passkeys by exploiting missing authentication in the /api/webauthn/prepare and /api/webauthn/register endpoints. Attackers can replace existing passkeys, gaining persistent passwordless login access that remains even after password changes or resets.

Detection Guidance

Check phpMyFAQ logs for unusual passkey enrollment activity via /api/webauthn/prepare and /api/webauthn/register endpoints. Look for sessions without step-up authentication. Verify if passkeys were added without user consent by checking the webauthnkeys field in the database.

Impact Analysis

If your phpMyFAQ account is affected, an attacker with a hijacked session could replace your passkeys and gain full, persistent access to your account. This includes administrative accounts, allowing full takeover. The attack survives password changes and lacks UI or email notifications for passkey changes.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Persistent unauthorized access may result in non-compliance with access control and audit logging mandates.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.1.12 or 4.2.0-RC.2 or later. Ensure step-up authentication is enforced before passkey enrollment. Review and revoke unauthorized passkeys using the new revokeWebAuthnKeys() method. Monitor for suspicious passkey additions via email notifications.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130370. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...