CVE-2026-80211

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

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

FrontAccounting through 2.4.20 stores and verifies user passwords as unsalted MD5 digests. admin/users.php passes md5($_POST['password']) to add_user() and update_user_password(), admin/change_current_user_password.php does the same when a user changes their own password, the forgotten-password path in includes/current_user.inc hashes the newly generated password the same way, and authentication calls get_user_auth($loginname, md5($password)). The codebase applies no per-password salt and contains no call to password_hash(), password_verify() or any other adaptive hash, so identical passwords yield identical digests and an attacker who obtains the user table can recover plaintext passwords with precomputed lookup tables or high-rate GPU cracking.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/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 computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 29, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage | Advisories | VulnCheck

https://www.vulncheck.com/advisories/frontaccounting-through-2.4.20-use-of-unsalted-md5-for-password-storage
generic

FA/includes/current_user.inc at 9464a3ffef03c139d9396e697bce9a0a9f131a72 · FrontAccountingERP/FA · GitHub

https://github.com/FrontAccountingERP/FA/blob/9464a3ffef03c139d9396e697bce9a0a9f131a72/includes/current_user.inc#L79
generic

GitHub - FrontAccountingERP/FA: Official FrontAccounting mirror repository · GitHub

https://github.com/FrontAccountingERP/FA
generic

oss/FA.md at main · geo-chen/oss · GitHub

https://github.com/geo-chen/oss/blob/main/FA.md#finding-2-unsalted-md5-password-hashing-in-frontaccounting

Vendor Advisories for CVE-2026-80211(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 13× in last 7d / 13× 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.

  1. 2026-08-30 03:09 UTCEG score recompute
  2. 2026-08-30 03:09 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 04:30 UTCEG score recompute
  5. 2026-08-29 04:29 UTCGHSA enrichment
  6. 2026-08-29 03:19 UTCEG score recompute
  7. 2026-08-29 03:18 UTCGHSA enrichment
  8. 2026-08-28 21:42 UTCEPSS rescore
  9. 2026-08-28 16:07 UTCEG score recompute
  10. 2026-08-28 16:07 UTCGHSA enrichment
  11. 2026-08-27 17:27 UTCEG score recompute
  12. 2026-08-27 16:47 UTCEG score recompute
  13. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80211?
CVE-2026-80211 is a medium vulnerability published on August 27, 2026. FrontAccounting through 2.4.20 stores and verifies user passwords as unsalted MD5 digests. admin/users.php passes md5($POST['password']) to adduser() and updateuserpassword(), admin/changecurrentuserpassword.php does the same when a user changes their own password, the forgotten-password path in…
When was CVE-2026-80211 disclosed?
CVE-2026-80211 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80211 actively exploited?
CVE-2026-80211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.6% of all scored CVEs.
What is the CVSS score of CVE-2026-80211?
CVE-2026-80211 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-80211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80211, 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-80211

Explore →

Is Your Infrastructure Affected by CVE-2026-80211?

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

Start Free Scan →Browse All CVEs