FrontAccounting < 2.4.20 SQL Injection via get_gl_transactions()
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.2epss 0.3%
exploitation probability
0.3%top 80% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
FrontAccounting before 2.4.20 contains a SQL injection vulnerability in the get_gl_transactions() function where the filter_type parameter is concatenated directly into a SQL IN() clause without parameterization. Attackers with SA_GLANALYTIC permission can inject arbitrary SQL by supplying a closing parenthesis followed by malicious conditions to extract sensitive journal entry data through boolean-based blind SQL injection with reliable response size differentials.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
Affected products
FrontAccounting · FrontAccountingpublic PoCs found — 1
cve_referencejivasecurity.com/writeups/frontaccounting-sqli-journal-entries-report-cve-2026-40524unverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/FrontAccountingERP/FA/commit/647a18196caad27f96ea852e993c9e30f815357fhttps://jivasecurity.com/writeups/frontaccounting-sqli-journal-entries-report-cve-2026-40524https://sourceforge.net/p/frontaccounting/news/2026/04/release-2420/https://www.vulncheck.com/advisories/frontaccounting-sql-injection-via-get-gl-transactions