# CVE-2026-70370: Koha - SQL Injection in reports/catalogue_stats.pl

> Attackers can execute arbitrary SQL commands via the Line and Column parameters in catalogue_stats.pl, potentially reading or modifying database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 4 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-8rx2-c3qm-2mc4

## What is CVE-2026-70370?

CVE-2026-70370 is a high-severity SQL injection vulnerability in Koha, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Koha's reports/catalogue_stats.pl builds dynamic SQL in sub calculate by interpolating the user-controlled Line and Column request parameters directly into identifier positions of the query (SELECT DISTINCTROW, GROUP BY, ORDER BY) with no whitelist validation.

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

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


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

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

## Is CVE-2026-70370 being exploited?

There is no known exploitation of CVE-2026-70370 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70370 is a high-severity SQL injection vulnerability in Koha, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70370 in the wild and no public exploit code.

Affected product: Koha. 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-70370/ (Markdown: https://insights.sbomify.com/CVE-2026-70370/index.md)
```

## Sources

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

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