CVE-2026-130362
Deferred Deferred - Pending Action

phpMyFAQ Account Enumeration via WebAuthn API

Vulnerability report for CVE-2026-130362, 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 an account enumeration vulnerability that allows unauthenticated attackers to identify valid logins through differing POST /api/webauthn/prepare responses. Attackers can submit wordlists of usernames, reusing one unconsumed CSRF token without rate limiting, to discover administrator logins for password spraying and phishing.

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 4 associated CPEs
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.12 (exc)
phpmyfaq phpmyfaq 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-204 The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an account enumeration vulnerability in phpMyFAQ versions 4.1.9 through 4.1.11 and 4.2.0-alpha through 4.2.0-RC.1. It allows unauthenticated attackers to identify valid usernames by exploiting differences in server responses from the POST /api/webauthn/prepare endpoint. Attackers can submit lists of usernames and reuse a single CSRF token without rate limiting to discover administrator accounts for further attacks.

Detection Guidance

To detect this vulnerability, monitor the /api/webauthn/prepare endpoint for unusual activity. Attackers may send repeated requests with different usernames to identify valid accounts. Check server logs for repeated POST requests to this endpoint with varying usernames and a single reused CSRF token.

Impact Analysis

This vulnerability enables attackers to identify valid administrator accounts through password spraying or phishing campaigns. It does not grant direct access but provides reconnaissance to target high-privilege accounts. The impact is higher if WebAuthn support is enabled or registration is open.

Compliance Impact

This vulnerability could indirectly impact compliance with GDPR and HIPAA by enabling attackers to identify valid user accounts, including administrators. This reconnaissance could lead to further attacks like password spraying or phishing, potentially compromising personal data or protected health information if such accounts have elevated access. GDPR requires protecting personal data and preventing unauthorized access, while HIPAA mandates safeguarding protected health information. The vulnerability does not directly violate these standards but creates a pathway for potential breaches that could result in non-compliance if exploited.

Mitigation Strategies

Immediately update phpMyFAQ to version 4.1.12 or 4.2.0-RC.2 or later. If updating is not possible, implement rate limiting on the /api/webauthn/prepare endpoint and ensure uniform error responses for all login attempts to prevent account enumeration.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130362. 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...