# CVE-2026-80210: FrontAccounting through 2.4.20 Cross-Site Request Forgery on Financial Transaction Forms

> Attackers can forge financial transactions and modify company settings by tricking authenticated users into submitting malicious forms due to missing CSRF validation.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-5wxj-x5xj-28rp

## What is CVE-2026-80210?

CVE-2026-80210 is a high-severity vulnerability in FrontAccounting, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-80210?


## How do I fix CVE-2026-80210?

No fix has been published for CVE-2026-80210 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80210 being exploited?

There is no known exploitation of CVE-2026-80210 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80210 and fix it if it is affected.

What it is: CVE-2026-80210 is a high-severity vulnerability in FrontAccounting, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-80210 in the wild and no public exploit code.

Affected product: FrontAccounting. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80210/ (Markdown: https://insights.sbomify.com/CVE-2026-80210/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80210
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80210
- OSV: https://osv.dev/vulnerability/CVE-2026-80210

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80210/
Summaries are generated and may contain mistakes; the official description above is the record.