phpMyFAQ is an open source FAQ web application. Versions 3.2.0 through 4.1.5 contain an authentication bypass in its public two-factor authentication verification flow: an unauthenticated attacker can submit an account’s numeric user ID and a valid or brute-forced six-digit TOTP code without first authenticating with the account password, allowing takeover of any 2FA-enabled account, including administrator accounts. Version 4.1.6 is patched by binding TOTP verification to a session established after successful password authentication and limiting failed TOTP attempts. No official workaround is documented; affected installations should upgrade to 4.1.6 or later.
CVE-2026-56737
HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.1Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(low)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
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 computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (4)
Auto-updated Sep 24, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available
commit 6a69f6e2142f (thorsten/phpMyFAQ)
Patch available: thorsten/phpMyFAQ 4.1-nightly-2026-09-09 (contains commit 6a69f6e2142f)
https://github.com/thorsten/phpMyFAQ/commit/6a69f6e2142fde722165c65b7e0a49f3176e87begithub_commit Patch Available
commit 5097dff341fb (thorsten/phpMyFAQ)
Patch available: thorsten/phpMyFAQ 4.1-nightly-2026-09-09 (contains commit 5097dff341fb)
https://github.com/thorsten/phpMyFAQ/commit/5097dff341fb01e93e8561e7261b3ae657df715agithub_commit Patch Available
commit 410208b90f1d (thorsten/phpMyFAQ)
Patch available: thorsten/phpMyFAQ 4.1-nightly-2026-09-09 (contains commit 410208b90f1d)
https://github.com/thorsten/phpMyFAQ/commit/410208b90f1d01534812ac5203d3e8d9c7bd591fgithub Patch Available🟡 PoC Available
Two-factor authentication login bypasses the password factor · Advisory · thorsten/phpMyFAQ · GitHub
https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8gpw-xvpf-hvx5Vendor Advisories for CVE-2026-56737(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-09-24 16:35 UTCEG score recompute
- 2026-09-24 15:17 UTCEG score recompute
- 2026-09-24 15:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-56737?
CVE-2026-56737 is a high vulnerability published on September 24, 2026. phpMyFAQ is an open source FAQ web application. Versions 3.2.0 through 4.1.5 contain an authentication bypass in its public two-factor authentication verification flow: an unauthenticated attacker can submit an account’s numeric user ID and a valid or brute-forced six-digit TOTP code without first…
When was CVE-2026-56737 disclosed?
CVE-2026-56737 was first published in the National Vulnerability Database on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-56737?
CVE-2026-56737 has a CVSS v3 base score of 8.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-56737?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56737, 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
Explore the affected products and dependency analysis for CVE-2026-56737
Is Your Infrastructure Affected by CVE-2026-56737?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.