# CVE-2026-40523: FrontAccounting < 2.4.20 SQL Injection via reporting/rep710.php

> Authenticated attackers with specific permissions can execute arbitrary SQL queries to extract data or cause denial of service in FrontAccounting.

- **Severity:** High 7.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-8ccm-j5hq-9jhr

## What is CVE-2026-40523?

CVE-2026-40523 is a high-severity SQL injection vulnerability in FrontAccounting, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FrontAccounting before 2.4.20 contains a SQL injection vulnerability in the Audit Trail report handler that allows authenticated attackers with SA_GLANALYTIC permission to execute arbitrary SQL queries by injecting malicious code into the PARAM_2 and PARAM_3 POST parameters. Attackers can exploit time-based blind SQL injection through SLEEP() functions that are amplified across JOIN result sets to cause denial of service by exhausting database connections, or extract arbitrary database content through UNION-based injection techniques.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-40523?


## How do I fix CVE-2026-40523?

No fix has been published for CVE-2026-40523 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40523 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40523 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40523 and fix it if it is affected.

What it is: CVE-2026-40523 is a high-severity SQL injection vulnerability in FrontAccounting, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40523 exists.

Affected product: FrontAccounting. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40523/ (Markdown: https://insights.sbomify.com/CVE-2026-40523/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40523
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40523
- OSV: https://osv.dev/vulnerability/CVE-2026-40523

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40523/
Summaries are generated and may contain mistakes; the official description above is the record.