Is CVE-2026-80210 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-80210 being exploited in the wild.

How severe is CVE-2026-80210?

Medium severity, with a CVSS score of 6.5, published 27 August 2026.

Which products and versions are affected?

FrontAccounting through 2.4.20.

Is there a fix for CVE-2026-80210?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-80210 attacked?

It is attacked over the network.

Am I affected by CVE-2026-80210?

Check whether you run FrontAccounting at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-80210: FrontAccounting CSRF in financial transaction handlers

CVE-2026-80210 · Severity: medium · CVSS 6.5 · Published 2026-08-27

FrontAccounting is an open-source web-based accounting and ERP system used for invoicing, banking, and financial management. The application generates CSRF tokens on forms but fails to validate them in critical financial transaction endpoints (journal entries, invoices, payments, bank transactions). An attacker can trick an authenticated user into loading a malicious page and auto-submit forged transactions that will be executed under the victim's session, resulting in unauthorized journal entries, invoices, payments, or company configuration changes.

Technologies: FrontAccounting. Vendors: FrontAccounting.

Quick answers

Is CVE-2026-80210 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-80210 being exploited in the wild.
How severe is CVE-2026-80210?: Medium severity, with a CVSS score of 6.5, published 27 August 2026.
Which products and versions are affected?: FrontAccounting through 2.4.20.
Is there a fix for CVE-2026-80210?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-80210 attacked?: It is attacked over the network.
Am I affected by CVE-2026-80210?: Check whether you run FrontAccounting at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

FrontAccounting implements CSRF token generation in the end_form() function (includes/ui/ui_controls.inc) and embeds tokens as a _token hidden field in every form. However, token validation via check_csrf_token() is performed only in admin/users.php and admin/change_current_user_password.php. Critical financial transaction handlers 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 do not validate the CSRF token, leaving them vulnerable to cross-origin request forgery attacks. An attacker who can get an authenticated user to visit a malicious page can auto-submit a form to any of these endpoints and have transactions recorded without origin verification. A patch would require adding check_csrf_token() calls to all unprotected financial endpoints.

Affected products

FrontAccounting FrontAccounting through 2.4.20

Timeline

2026-08-27: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.