CVE-2026-80210

6th percentile - higher than 6% of all known CVEs

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.

Lack of CSRF token validation in critical financial operations allows an attacker to perform unauthorized transactions and configuration changes on behalf of the victim, potentially leading to financial loss and data integrity issues.

Apply a patch that adds CSRF token validation to all financial and configuration transaction handlers, and consider implementing additional protections such as Origin header checks.