CVE-2026-130362

phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Account Enumeration via WebAuthn Prepare

Published Nov 17, 2026 CVSS 4.0 · 6.9 Medium 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 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.

Analysis

AI-generated

Technical impact

The flaw occurs during the WebAuthn Prepare API call in phpMyFAQ, where different responses are returned for valid versus invalid usernames. An unauthenticated attacker can send a list of candidate usernames and, by reusing a single CSRF token and without any rate limiting, detect which accounts exist. The information disclosed can be used for targeted password spraying and phishing attacks against administrators.

Affected Systems

phpMyFAQ versions 4.1.9 through 4.1.11 and 4.2.0-alpha through 4.2.0-RC.1 installed by vendors including thorsten. The issue is present in the WebAuthn prepare endpoint of the phpMyFAQ application.

Risk and Exploitability

The CVSS v3.1 base score of 6.9 classifies this as a medium-impact flaw; it grants unauthenticated users the ability to enumerate accounts via a simple HTTP POST request. The EPSS score is not available, and the vulnerability is not listed in CISA's KEV catalog, indicating no confirmed exploitation yet. However, the lack of rate limiting and CSRF token consumption combined with the widespread use of phpMyFAQ make this risk noteworthy for administrators, especially those with active WebAuthn support.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.12 or later, or 4.2.0-RC.2 or later.
  • Restrict access to the /api/webauthn/prepare endpoint to authenticated sessions or IP whitelisting.
  • Implement rate limiting on that endpoint and enforce CSRF token consumption to prevent bulk enumeration.

Generated by OpenCVE AI on November 17, 2026 at 02:29 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 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.
Title phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Account Enumeration via WebAuthn Prepare
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-204
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses
  • CWE-204

    Observable Response Discrepancy

Sources

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