Vulnerability Description
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 Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/FrontAccountingERP/FA
- https://github.com/FrontAccountingERP/FA/blob/9464a3ffef03c139d9396e697bce9a0a9f
- https://github.com/geo-chen/oss/blob/main/FA.md#finding-1-cross-site-request-for
- https://www.vulncheck.com/advisories/frontaccounting-through-2.4.20-cross-site-r
FAQ
What is CVE-2026-80210?
CVE-2026-80210 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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...
How severe is CVE-2026-80210?
CVE-2026-80210 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-80210?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.