CVE-2026-80210
FrontAccounting through 2.4.20 generates a CSRF token in end_form() …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/FrontAccountingERP/FA
- github.com/FrontAccountingERP/FA/blob/9464a3ffef03c139d9396e697bce9a0a9f131a72/includes/ui
- github.com/geo-chen/oss/blob/main/FA.md#finding-1-cross-site-request-forgery-on-financial-
- www.vulncheck.com/advisories/frontaccounting-through-2.4.20-cross-site-request-forgery-on-
- nvd.nist.gov/vuln/detail/CVE-2026-80210
- cve.org/CVERecord?id=CVE-2026-80210
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.