CVE-2026-80210

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. The CNA's CVSS baseline 6.5; 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
6.5EG
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.2%CVSS: 6.5Exploit: 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 generates a CSRF token in end_form() in includes/ui/ui_controls.inc and embeds it as the _token hidden field in every form it renders, but only admin/users.php and admin/change_current_user_password.php call check_csrf_token() to validate it. No financial transaction handler validates the token, including gl/gl_journal.php, gl/gl_bank.php, purchasing/supplier_invoice.php, sales/customer_invoice.php, sales/customer_payments.php and admin/company_preferences.php, so those endpoints act on POST data with no origin check. An attacker who gets an authenticated user to load a page under attacker control can auto-submit a cross-origin form to any of them and have the forged journal entry, invoice, customer payment, bank transaction or company configuration change recorded under the victim's session.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation0.2% × 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.2%
EPSS %ILE
11th
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 Cross-Site Request Forgery on Financial Transaction Forms | Advisories | VulnCheck

https://www.vulncheck.com/advisories/frontaccounting-through-2.4.20-cross-site-request-forgery-on-financial-transaction-forms
Web page

FA/includes/ui/ui_controls.inc at 9464a3ffef03c139d9396e697bce9a0a9f131a72 · FrontAccountingERP/FA · GitHub

https://github.com/FrontAccountingERP/FA/blob/9464a3ffef03c139d9396e697bce9a0a9f131a72/includes/ui/ui_controls.inc#L89
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-1-cross-site-request-forgery-on-financial-transaction-forms-in-frontaccounting

Vendor Advisories for CVE-2026-80210(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 / 85× 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 99 of 137 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 38 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.2% · 11th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 11th 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.2% · 11th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-10 01:56 UTCEG score recompute
  10. 2026-10-10 01:56 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-09 03:08 UTCEG score recompute
  13. 2026-10-09 03:07 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-08 01:21 UTCEG score recompute
  16. 2026-10-08 01:20 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-06 22:57 UTCEG score recompute
  19. 2026-10-06 22:57 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-06 00:54 UTCEG score recompute
  22. 2026-10-06 00:54 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-05 02:39 UTCEG score recompute
  25. 2026-10-05 02:39 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
Show 74 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-04 04:35 UTCEG score recompute
  3. 2026-10-04 04:35 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  4. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-03 06:31 UTCEG score recompute
  6. 2026-10-03 06:31 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  7. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-02 08:27 UTCEG score recompute
  9. 2026-10-02 08:27 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  10. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-01 10:23 UTCEG score recompute
  12. 2026-10-01 10:23 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  13. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-09-30 12:19 UTCEG score recompute
  15. 2026-09-30 12:19 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  16. 2026-09-29 14:15 UTCEG score recompute
  17. 2026-09-29 14:15 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  18. 2026-09-28 14:53 UTCEG score recompute
  19. 2026-09-28 14:53 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  20. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-27 16:49 UTCEG score recompute
  22. 2026-09-27 16:49 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-09-26 18:45 UTCEG score recompute
  25. 2026-09-26 18:45 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  26. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-25 13:02 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  29. 2026-09-24 14:58 UTCEG score recompute
  30. 2026-09-24 14:58 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  31. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  32. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-09-23 17:25 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  34. 2026-09-22 21:45 UTCEG score recompute
  35. 2026-09-22 21:45 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  36. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-09-21 23:41 UTCEG score recompute
  38. 2026-09-21 23:41 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  39. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-09-21 01:38 UTCEG score recompute
  41. 2026-09-21 01:38 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-09-20 03:02 UTCEG score recompute
  44. 2026-09-20 03:02 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  45. 2026-09-19 04:58 UTCEG score recompute
  46. 2026-09-19 04:57 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  47. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-09-18 06:53 UTCEG score recompute
  49. 2026-09-18 06:53 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  50. 2026-09-17 08:49 UTCEG score recompute
  51. 2026-09-17 08:49 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  52. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-09-16 10:45 UTCEG score recompute
  54. 2026-09-16 10:45 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  55. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  56. 2026-09-15 12:28 UTCEG score recompute
  57. 2026-09-15 12:28 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  58. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  59. 2026-09-14 14:24 UTCEG score recompute
  60. 2026-09-14 14:24 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  61. 2026-09-13 16:20 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  62. 2026-09-12 18:16 UTCEG score recompute
  63. 2026-09-12 18:16 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  64. 2026-09-11 20:12 UTCEG score recompute
  65. 2026-09-11 20:12 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  66. 2026-09-10 22:04 UTCEG score recompute
  67. 2026-09-10 22:04 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  68. 2026-09-10 00:00 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  69. 2026-09-09 00:41 UTCEG score recompute
  70. 2026-09-09 00:41 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  71. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  72. 2026-09-07 22:25 UTCEG score recompute
  73. 2026-09-07 22:25 UTCGHSA enrichmentGHSA-5wxj-x5xj-28rp · GitHub severity HIGH · GitHub CVSS 6.5
  74. 2026-09-07 00:21 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80210?
CVE-2026-80210 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. FrontAccounting through 2.4.20 generates a CSRF token in endform() in includes/ui/uicontrols.inc and embeds it as the token hidden field in every form it renders, but only admin/users.php and admin/changecurrentuserpassword.php call checkcsrftoken() to validate it. No financial transaction handler…
When was CVE-2026-80210 made public?
CVE-2026-80210 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-80210 actively exploited?
CVE-2026-80210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80210?
CVE-2026-80210 has a CVSS base score of 6.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-80210?
No fix for CVE-2026-80210 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-80210 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80210

Explore →

Is Your Infrastructure Affected by CVE-2026-80210?

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

Book a Demo →Browse All CVEs