CVE-2026-45010

phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint

Published May 15, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
phpMyFAQ before 4.1.2 contains an improper restriction of excessive authentication attempts vulnerability in the /admin/check endpoint, which accepts arbitrary user-id parameters without session binding or rate limiting. Unauthenticated attackers can brute-force any user's six-digit TOTP code by submitting POST requests with sequential token values, bypassing two-factor authentication to gain full administrative access.

Analysis

AI-generated

Technical impact

phpMyFAQ before version 4.1.2 allows attackers to submit arbitrary user‑id parameters without any session binding or rate limiting to the /admin/check endpoint. This flaw permits an unauthenticated attacker to brute‑force a victim’s six‑digit TOTP code by sequentially trying all possible tokens. Successful exploitation grants full administrative control, compromising the confidentiality and integrity of the entire instance.

Affected Systems

The vulnerability affects installations of phpMyFAQ prior to the 4.1.2 release. Any server hosting a version before 4.1.2 and exposing the /admin/check endpoint is impacted.

Risk and Exploitability

The CVSS score of 9.3 indicates a critical severity, and with an EPSS score of < 1% indicating a very low exploitation probability, the lack of rate limiting and session checks suggest that while exploitation is possible, the actual exploitation probability remains low. The vulnerability is not on the CISA KEV list, but the straightforward attack vector—unauthenticated POST requests—reduces the required skill level for attackers.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.2 or newer, which removes the unauthenticated access to the /admin/check endpoint.
  • Block or restrict POST requests to /admin/check for non‑authenticated sessions using a firewall or web‑application firewall rule, limiting the number of requests from a single IP.
  • As a temporary measure, alter the configuration to require a valid session or authenticated user ID before processing /admin/check requests, or disable the endpoint entirely until the patch is applied.

Generated by OpenCVE AI on May 28, 2026 at 17:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-9pq7-mfwh-xx2j phpMyFAQ enables unauthenticated 2FA brute-force attack via /admin/check acceptance of arbitrary user-id
History
Type Values Removed Values Added
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
Metrics cvssV4_0

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

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq
Type Values Removed Values Added
Description phpMyFAQ before 4.1.2 contains an improper restriction of excessive authentication attempts vulnerability in the /admin/check endpoint, which accepts arbitrary user-id parameters without session binding or rate limiting. Unauthenticated attackers can brute-force any user's six-digit TOTP code by submitting POST requests with sequential token values, bypassing two-factor authentication to gain full administrative access.
Title phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint
Weaknesses CWE-307
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-307

    Improper Restriction of Excessive Authentication Attempts

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 8, 2026, 2:03 PM
Reserved
May 8, 2026, 4:43 PM
Status
Deferred
Published
May 15, 2026, 7:17 PM
Modified
Oct 26, 2026, 2:10 PM