CVE-2026-40522: high-severity vulnerability in FrontAccounting
FrontAccounting < 2.4.20 SQL Injection via rep601.php
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.1epss 0.2%
FrontAccounting before 2.4.20 contains a SQL injection vulnerability in the Bank Statement report handler that allows authenticated attackers to extract arbitrary database data by injecting UNION SELECT payloads into the PARAM_0 POST parameter. Attackers can supply malicious SQL syntax through the unparameterized WHERE clause to retrieve sensitive information including usernames, password hashes, and email addresses from the users table, rendered into PDF report output.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
FrontAccounting · FrontAccountingpublic PoCs found — 1
cve_referencejivasecurity.com/writeups/frontaccounting-sqli-bank-statement-report-cve-2026-40522unverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — FrontAccounting
In the same product, most dangerous first.
CVE-2026-40521HIGHFrontAccounting < 2.4.20 Path Traversal RCE via attachment uploadEPSS 1.0%CVE-2026-40523HIGHFrontAccounting < 2.4.20 SQL Injection via reporting/rep710.phpEPSS 0.5%CVE-2026-40524HIGHFrontAccounting < 2.4.20 SQL Injection via get_gl_transactions()EPSS 0.3%CVE-2026-80211HIGHFrontAccounting through 2.4.20 Use of Unsalted MD5 for Password StorageEPSS 0.3%CVE-2026-80210HIGHFrontAccounting through 2.4.20 Cross-Site Request Forgery on Financial Transaction FormsEPSS 0.2%