Forged financial transactions via unchecked CSRF tokens
Published Aug 27, 2026 · Updated Aug 27, 2026
Cross-site request forgery in FrontAccounting through 2.4.20 allows remote attackers to forge financial transactions via a victim's session. Financial and administrative POST handlers do not call check_csrf_token(), so they accept cross-origin requests without validating the generated _token. The victim must be authenticated and load attacker-controlled content; forged entries and configuration changes run with the victim's permissions.
Summary
What happened
Cross-site request forgery in FrontAccounting through 2.4.20 allows remote attackers to forge financial transactions via a victim's session. Financial and administrative POST handlers do not call check_csrf_token(), so they accept cross-origin requests without validating the generated _token. The victim must be authenticated and load attacker-controlled content; forged entries and configuration changes run with the victim's permissions.
The record
- CVE
- CVE-2026-80210
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- FrontAccounting
- Product
- FrontAccounting
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.20
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo