CVE-2026-45010

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-15. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
26.4%
KEV
Not listed

Published

May 15, 2026

Last Modified

May 28, 2026

Advisory Details (2)

Auto-updated May 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unauthenticated 2FA brute-force via /admin/check accepting arbitrary user-id · Advisory · thorsten/phpMyFAQ · GitHub

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9pq7-mfwh-xx2j
generic

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

https://www.vulncheck.com/advisories/phpmyfaq-unauthenticated-two-factor-authentication-brute-force-via-admin-check-endpoint

Vendor Advisories for CVE-2026-45010(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
phpmyfaq/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)4.1.2
thorsten/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)4.1.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 129 total refreshes for this CVE.

  1. 2026-07-23 03:16 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-18 00:59 UTCOSV refresh
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 03:08 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-19 19:25 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-17 17:53 UTCEPSS rescore
  17. 2026-06-16 17:52 UTCEPSS rescore
  18. 2026-06-15 17:49 UTCEPSS rescore
  19. 2026-06-13 23:00 UTCEPSS rescore
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-10 22:18 UTCEPSS rescore
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-08 23:38 UTCGHSA enrichment
  27. 2026-06-08 19:46 UTCGHSA enrichment
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-08 12:13 UTCGHSA enrichment
  31. 2026-06-08 08:20 UTCGHSA enrichment
  32. 2026-06-08 04:28 UTCGHSA enrichment
  33. 2026-06-08 00:35 UTCGHSA enrichment
  34. 2026-06-07 20:43 UTCGHSA enrichment
  35. 2026-06-07 16:50 UTCGHSA enrichment
  36. 2026-06-07 15:25 UTCEPSS rescore
  37. 2026-06-07 15:25 UTCEPSS rescore
  38. 2026-06-07 12:57 UTCGHSA enrichment
  39. 2026-06-07 09:04 UTCGHSA enrichment
  40. 2026-06-07 05:11 UTCGHSA enrichment
  41. 2026-06-07 01:19 UTCGHSA enrichment
  42. 2026-06-06 21:26 UTCGHSA enrichment
  43. 2026-06-06 17:33 UTCGHSA enrichment
  44. 2026-06-06 13:47 UTCEPSS rescore
  45. 2026-06-06 13:47 UTCEPSS rescore
  46. 2026-06-06 13:40 UTCGHSA enrichment
  47. 2026-06-06 09:48 UTCGHSA enrichment
  48. 2026-06-06 05:55 UTCGHSA enrichment
  49. 2026-06-06 02:02 UTCGHSA enrichment
  50. 2026-06-05 22:47 UTCEPSS rescore
  51. 2026-06-05 22:09 UTCGHSA enrichment
  52. 2026-06-05 18:15 UTCGHSA enrichment
  53. 2026-06-05 14:22 UTCGHSA enrichment
  54. 2026-06-05 10:28 UTCGHSA enrichment
  55. 2026-06-05 06:35 UTCGHSA enrichment
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-05 06:10 UTCEPSS rescore
  58. 2026-06-05 02:42 UTCGHSA enrichment
  59. 2026-06-04 22:49 UTCGHSA enrichment
  60. 2026-06-04 18:56 UTCGHSA enrichment
  61. 2026-06-04 15:03 UTCGHSA enrichment
  62. 2026-06-04 13:12 UTCEPSS rescore
  63. 2026-06-04 13:12 UTCEPSS rescore
  64. 2026-06-04 11:10 UTCGHSA enrichment
  65. 2026-06-04 07:17 UTCGHSA enrichment
  66. 2026-06-04 03:24 UTCGHSA enrichment
  67. 2026-06-03 23:31 UTCGHSA enrichment
  68. 2026-06-03 19:38 UTCGHSA enrichment
  69. 2026-06-03 15:45 UTCGHSA enrichment
  70. 2026-06-03 11:52 UTCGHSA enrichment
  71. 2026-06-03 07:59 UTCGHSA enrichment
  72. 2026-06-03 04:06 UTCGHSA enrichment
  73. 2026-06-03 00:13 UTCGHSA enrichment
  74. 2026-06-02 20:20 UTCGHSA enrichment
  75. 2026-06-02 20:13 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-45010?
CVE-2026-45010 is a critical vulnerability published on May 15, 2026. 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…
When was CVE-2026-45010 disclosed?
CVE-2026-45010 was first published in the National Vulnerability Database on May 15, 2026, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45010 actively exploited?
CVE-2026-45010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45010?
CVE-2026-45010 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-45010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45010, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45010

Explore →

Is Your Infrastructure Affected by CVE-2026-45010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.