CVE-2026-40524

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

FrontAccounting < 2.4.20 SQL Injection via get_gl_transactions() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/frontaccounting-sql-injection-via-get-gl-transactions
generic

Closing the Parenthesis: Boolean SQLi via IN() Clause Injection in FrontAccounting — Jiva Security

https://jivasecurity.com/writeups/frontaccounting-sqli-journal-entries-report-cve-2026-40524
github_commit

commit 647a18196caa (FrontAccountingERP/FA)

Fix landed in FrontAccountingERP/FA commit 647a18196caa — awaiting tagged release

https://github.com/FrontAccountingERP/FA/commit/647a18196caad27f96ea852e993c9e30f815357f

Vendor 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.

  1. 2026-07-06 22:01 UTCEG score recompute
  2. 2026-07-06 22:01 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:00 UTCEG score recompute
  6. 2026-07-06 11:00 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 23:55 UTCEG score recompute
  10. 2026-07-05 23:55 UTCGHSA enrichment
  11. 2026-07-05 12:55 UTCEG score recompute
  12. 2026-07-05 12:55 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 01:54 UTCEG score recompute
  15. 2026-07-05 01:54 UTCGHSA enrichment
  16. 2026-07-04 14:54 UTCEG score recompute
  17. 2026-07-04 14:54 UTCGHSA enrichment
  18. 2026-07-04 03:53 UTCEG score recompute
  19. 2026-07-04 03:53 UTCGHSA enrichment
  20. 2026-07-03 16:37 UTCEG score recompute
  21. 2026-07-03 16:37 UTCGHSA enrichment
  22. 2026-07-03 05:37 UTCEG score recompute
  23. 2026-07-03 05:37 UTCGHSA enrichment
  24. 2026-07-02 18:38 UTCEG score recompute
  25. 2026-07-02 18:38 UTCGHSA enrichment
Show 16 more
  1. 2026-07-02 07:37 UTCEG score recompute
  2. 2026-07-02 07:37 UTCGHSA enrichment
  3. 2026-07-01 20:38 UTCEG score recompute
  4. 2026-07-01 20:37 UTCGHSA enrichment
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 09:37 UTCEG score recompute
  7. 2026-07-01 09:37 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 22:37 UTCEG score recompute
  10. 2026-06-30 22:37 UTCGHSA enrichment
  11. 2026-06-30 11:37 UTCEG score recompute
  12. 2026-06-30 11:36 UTCGHSA enrichment
  13. 2026-06-30 00:33 UTCEG score recompute
  14. 2026-06-30 00:33 UTCGHSA enrichment
  15. 2026-06-29 13:33 UTCEG score recompute
  16. 2026-06-29 13:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-40524?
CVE-2026-40524 is a high vulnerability published on June 29, 2026. FrontAccounting before 2.4.20 contains a SQL injection vulnerability in the getgltransactions() function where the filtertype parameter is concatenated directly into a SQL IN() clause without parameterization. Attackers with SAGLANALYTIC permission can inject arbitrary SQL by supplying a closing…
When was CVE-2026-40524 disclosed?
CVE-2026-40524 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40524 actively exploited?
CVE-2026-40524 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40524?
CVE-2026-40524 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-40524?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40524, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-40524

Explore →

Is Your Infrastructure Affected by CVE-2026-40524?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.