CVE-2026-40522

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.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 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 v3
7.1
EG Score
7.1(high)
EPSS
4.4%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 29, 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 rep601.php | Advisories | VulnCheck

https://www.vulncheck.com/advisories/frontaccounting-sql-injection-via-rep601-php
generic

SQL Injection in FrontAccounting's Reporting Engine: Your Credentials, Rendered as a PDF — Jiva Security

https://jivasecurity.com/writeups/frontaccounting-sqli-bank-statement-report-cve-2026-40522
github_commit

commit 894adaf71393 (FrontAccountingERP/FA)

Fix landed in FrontAccountingERP/FA commit 894adaf71393 — awaiting tagged release

https://github.com/FrontAccountingERP/FA/commit/894adaf71393e0ef6a04fe6036fcd2464050f590

Vendor Advisories for CVE-2026-40522(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 38× in last 7d / 42× 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-07 05:44 UTCEG score recompute
  2. 2026-07-07 05:44 UTCGHSA enrichment
  3. 2026-07-06 18:54 UTCEG score recompute
  4. 2026-07-06 18:54 UTCGHSA enrichment
  5. 2026-07-06 08:00 UTCEG score recompute
  6. 2026-07-06 08:00 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 21:09 UTCEG score recompute
  10. 2026-07-05 21:09 UTCGHSA enrichment
  11. 2026-07-05 10:18 UTCEG score recompute
  12. 2026-07-05 10:18 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 23:29 UTCEG score recompute
  15. 2026-07-04 23:29 UTCGHSA enrichment
  16. 2026-07-04 12:40 UTCEG score recompute
  17. 2026-07-04 12:40 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 01:51 UTCEG score recompute
  20. 2026-07-04 01:50 UTCGHSA enrichment
  21. 2026-07-03 15:01 UTCEG score recompute
  22. 2026-07-03 15:00 UTCGHSA enrichment
  23. 2026-07-03 04:11 UTCEG score recompute
  24. 2026-07-03 04:11 UTCGHSA enrichment
  25. 2026-07-02 17:22 UTCEG score recompute
Show 17 more
  1. 2026-07-02 17:22 UTCGHSA enrichment
  2. 2026-07-02 06:33 UTCEG score recompute
  3. 2026-07-02 06:33 UTCGHSA enrichment
  4. 2026-07-01 19:41 UTCEG score recompute
  5. 2026-07-01 19:41 UTCGHSA enrichment
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 08:52 UTCEG score recompute
  8. 2026-07-01 08:52 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 22:03 UTCEG score recompute
  11. 2026-06-30 22:03 UTCGHSA enrichment
  12. 2026-06-30 11:14 UTCEG score recompute
  13. 2026-06-30 11:14 UTCGHSA enrichment
  14. 2026-06-30 00:22 UTCEG score recompute
  15. 2026-06-30 00:22 UTCGHSA enrichment
  16. 2026-06-29 13:33 UTCEG score recompute
  17. 2026-06-29 13:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-40522?
CVE-2026-40522 is a high vulnerability published on June 29, 2026. 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…
When was CVE-2026-40522 disclosed?
CVE-2026-40522 was first published in the National Vulnerability Database on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40522 actively exploited?
CVE-2026-40522 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40522?
CVE-2026-40522 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-40522?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40522, 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-40522

Explore →

Is Your Infrastructure Affected by CVE-2026-40522?

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