Home

Description

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.

PUBLISHED Reserved 2026-04-13 | Published 2026-06-29 | Updated 2026-07-14 | Assigner VulnCheck




HIGH: 7.1CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

HIGH: 7.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Problem types

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Use of Password Hash With Insufficient Computational Effort

Product status

Default status
affected

Any version before 2.4.20
affected

894adaf71393e0ef6a04fe6036fcd2464050f590 (git)
unaffected

Credits

Jiva (JivaSecurity) finder

References

jivasecurity.com/...qli-bank-statement-report-cve-2026-40522 technical-description exploit

sourceforge.net/p/frontaccounting/news/2026/04/release-2420/ release-notes

github.com/...ommit/894adaf71393e0ef6a04fe6036fcd2464050f590 patch

www.vulncheck.com/...accounting-sql-injection-via-rep601-php third-party-advisory

cve.org (CVE-2026-40522)

nvd.nist.gov (CVE-2026-40522)

Download JSON