CVE-2026-80211

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. The CNA's CVSS baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists FrontAccounting versions up to and including 2.4.20 as affected. No release containing a fix is confirmed on record.

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.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

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 (value × EchelonGraph’s weight)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
No fix on record yet.
Web page

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
Web page

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

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

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

https://github.com/FrontAccountingERP/FA
Web page

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 17× in last 7d / 80× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 130 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80211?
CVE-2026-80211 is a medium-severity vulnerability; its CVE record was 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 made public?
CVE-2026-80211 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-80211 actively exploited?
CVE-2026-80211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80211?
CVE-2026-80211 has a CVSS base score of 5.9 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-80211?
No fix for CVE-2026-80211 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists FrontAccounting versions up to and including 2.4.20 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-80211 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs