CVE-2026-80210

FrontAccounting through 2.4.20 Cross-Site Request Forgery on Financial Transaction Forms

Published Aug 27, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

FrontAccounting versions up to 2.4.20 implement a CSRF token for every form but only the administrative user‑management pages validate it. The financial transaction handlers—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—lack this validation, so they process POST data without any origin or authenticity check. An attacker who tricks an authenticated user into loading a malicious page can automatically submit a cross‑origin form to any of these endpoints, creating or altering journal entries, invoices, payments, bank transactions, or company settings under the victim’s session. The flaw is a classic type‑III Cross‑Site Request Forgery (CWE‑352) that allows untrusted actions to be performed with the victim’s privileges.

Affected Systems

The affected product is FrontAccounting, supplied by the vendor FrontAccounting. All releases through and including version 2.4.20 contain the flaw. The vulnerability specifically impacts the financial transaction handlers mentioned above, which are part of one or more public or internal forms for journal entries, bank transactions, supplier invoices, customer invoices, customer payments, and company preferences.

Risk and Exploitability

The CVSS score of 7.1 indicates a high severity vulnerability. The EPSS score is not available, and the issue is not listed in CISA KEV, suggesting no confirmed widespread exploitation yet. The attack requires an authenticated user session; the attacker must be able to deliver a malicious page that submits a form to the target endpoint. Successful exploitation would allow the attacker to insert or modify financial records, potentially leading to significant integrity and accounting errors for the affected organization.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade FrontAccounting to version 2.4.21 or newer, which adds CSRF validation to all financial transaction handlers.
  • If an upgrade is not immediately possible, manually insert a call to check_csrf_token() in each affected handler (e.g., 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).
  • Restrict access to the affected forms to users with the Administrator role, and enforce re‑authentication or an additional authorization step for sensitive actions.

Generated by OpenCVE AI on August 27, 2026 at 18:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title FrontAccounting through 2.4.20 Cross-Site Request Forgery on Financial Transaction Forms
First Time appeared Frontaccounting
Frontaccounting frontaccounting
Weaknesses CWE-352
CPEs cpe:2.3:a:frontaccounting:frontaccounting:*:*:*:*:*:*:*:*
Vendors & Products Frontaccounting
Frontaccounting frontaccounting
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:19 PM
Reserved
Aug 25, 2026, 11:15 PM
Status
Deferred
Published
Aug 27, 2026, 5:20 PM
Modified
Sep 23, 2026, 5:17 PM