# CVE-2026-72608: Koha Community Koha - Stored SQL Injection via Patron Card Layout image_name

> Authenticated staff can execute arbitrary SQL via patron card layout fields, allowing attackers to read the entire database including patron PII and password hashes.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-xg24-96fx-vx3g

## What is CVE-2026-72608?

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

### Official description

A stored SQL injection vulnerability in Koha through 24.11.17, 25.05.12, 25.11.06, and 26.05.01 allows authenticated staff with the tools => label_creator permission to execute arbitrary SQL via the image_name field of a patron card layout. The image_name value is stored verbatim in the layout XML and later concatenated raw into a SQL query in patroncards/create-pdf.pl when a patron card batch is printed. An attacker can read the entire Koha database including patron PII and staff bcrypt password hashes via error-based or time-based blind injection.

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

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


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

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

## Is CVE-2026-72608 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72608 is a medium-severity SQL injection vulnerability in Koha, published on 11 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-72608 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-72608/ (Markdown: https://insights.sbomify.com/CVE-2026-72608/index.md)
```

## Sources

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

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