PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-72608 Koha Community CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-11T12:17:43.987Z and has not been modified since then. CVE-2026-72608 describes a stored SQL injection vulnerability in Koha through 24.11.17, 25.05.12, 25.11.06, and 26.05.01. Authenticated staff with the tools => label_creator permission can execute arbitrary SQL via the image_name field of a patron card layout. The vulnerability arises from storing the image_name value verbatim in layout XML, later concatenated into a SQL query in patroncards/create-pdf.pl without sanitization. This allows error-based or time-based blind injection, potentially enabling an attacker to read the entire Koha database, including patron PII and staff bcrypt password hashes.

Vendor
Koha Community
Product
Koha
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-11
Original CVE updated
2026-08-28
Advisory published
2026-08-11
Advisory updated
2026-08-28

Who should care

Organizations using Koha versions through 24.11.17, 25.05.12, 25.11.06, and 26.05.01 should be aware of this vulnerability. Specifically, Koha administrators, IT staff responsible for database security, and information security professionals should take note of this CVE.

Technical summary

A stored SQL injection vulnerability exists in Koha versions through 24.11.17, 25.05.12, 25.11.06, and 26.05.01. An attacker with authenticated staff privileges and the tools => label_creator permission can execute arbitrary SQL queries via the image_name field of a patron card layout. The vulnerability arises from the verbatim storage of the image_name value in the layout XML, which is later concatenated into a SQL query in patroncards/create-pdf.pl without proper sanitization. This allows for error-based or time-based blind injection, potentially enabling an attacker to read the entire Koha database, including patron Personally Identifiable Information (PII) and staff bcrypt password hashes.

Defensive priority

Authenticated staff with label_creator permission may be able to execute arbitrary SQL queries, potentially leading to unauthorized data access.

Recommended defensive actions

  • Inventory and verify Koha versions through 24.11.17, 25.05.12, 25.11.06, and 26.05.01 for potential exposure.
  • Restrict label_creator permission to only necessary staff.
  • Monitor for suspicious database queries and error messages.
  • Implement compensating controls such as Web Application Firewalls (WAFs) to detect and prevent SQL injection attempts.
  • Apply vendor remediation when available.

Evidence notes

The vulnerability exists in Koha versions through 24.11.17, 25.05.12, 25.11.06, and 26.05.01. An attacker with tools => label_creator permission can 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. This allows for error-based or time-based blind injection, potentially enabling an attacker to read the entire Koha database, including patron PII and staff bcrypt password hashes.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-72608 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-72608

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-72608 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72608

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://koha-community.org/

    309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.