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.
CVE-2026-40524
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EPSS
- 19.4%
- KEV
- Not listed
Published
June 29, 2026
Last Modified
July 1, 2026
Advisory Details (4)
Auto-updated Jun 29, 2026FrontAccounting < 2.4.20 SQL Injection via get_gl_transactions() | Advisories | VulnCheck
https://www.vulncheck.com/advisories/frontaccounting-sql-injection-via-get-gl-transactionsFrontAccounting / News: Release 2.4.20
https://sourceforge.net/p/frontaccounting/news/2026/04/release-2420/Closing the Parenthesis: Boolean SQLi via IN() Clause Injection in FrontAccounting — Jiva Security
https://jivasecurity.com/writeups/frontaccounting-sqli-journal-entries-report-cve-2026-40524commit 647a18196caa (FrontAccountingERP/FA)
Fix landed in FrontAccountingERP/FA commit 647a18196caa — awaiting tagged release
https://github.com/FrontAccountingERP/FA/commit/647a18196caad27f96ea852e993c9e30f815357fVendor Advisories for CVE-2026-40524(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 37× in last 7d / 41× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 22:01 UTCEG score recompute
- 2026-07-06 22:01 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 11:00 UTCEG score recompute
- 2026-07-06 11:00 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:55 UTCEG score recompute
- 2026-07-05 23:55 UTCGHSA enrichment
- 2026-07-05 12:55 UTCEG score recompute
- 2026-07-05 12:55 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 01:54 UTCEG score recompute
- 2026-07-05 01:54 UTCGHSA enrichment
- 2026-07-04 14:54 UTCEG score recompute
- 2026-07-04 14:54 UTCGHSA enrichment
- 2026-07-04 03:53 UTCEG score recompute
- 2026-07-04 03:53 UTCGHSA enrichment
- 2026-07-03 16:37 UTCEG score recompute
- 2026-07-03 16:37 UTCGHSA enrichment
- 2026-07-03 05:37 UTCEG score recompute
- 2026-07-03 05:37 UTCGHSA enrichment
- 2026-07-02 18:38 UTCEG score recompute
- 2026-07-02 18:38 UTCGHSA enrichment
Show 16 moreShow fewer
- 2026-07-02 07:37 UTCEG score recompute
- 2026-07-02 07:37 UTCGHSA enrichment
- 2026-07-01 20:38 UTCEG score recompute
- 2026-07-01 20:37 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 09:37 UTCEG score recompute
- 2026-07-01 09:37 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 22:37 UTCEG score recompute
- 2026-06-30 22:37 UTCGHSA enrichment
- 2026-06-30 11:37 UTCEG score recompute
- 2026-06-30 11:36 UTCGHSA enrichment
- 2026-06-30 00:33 UTCEG score recompute
- 2026-06-30 00:33 UTCGHSA enrichment
- 2026-06-29 13:33 UTCEG score recompute
- 2026-06-29 13:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-40524?
When was CVE-2026-40524 disclosed?
Is CVE-2026-40524 actively exploited?
What is the CVSS score of CVE-2026-40524?
How do I remediate CVE-2026-40524?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-40524
Is Your Infrastructure Affected by CVE-2026-40524?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.