What is the CVSS score of CVE-2026-72610?

CVE-2026-72610 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2026-72610?

Yes, a patch is available for CVE-2026-72610. Update the affected software to the latest version immediately.

Koha ILS CVE-2026-72610

EUVD-2026-56131 MEDIUM

SQL Injection (CWE-89)

2026-08-11 TuranSec

GHSA-jjgf-vgv7-fgjv

Denial Of Service SQLi Koha Koha Community

4.3

CVSS 3.1 · Vendor: TuranSec

Severity by source

Vendor (TuranSec) PRIMARY

4.3 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

vuln.today AI

4.3 MEDIUM

Requires authenticated staff with edit_borrowers (PR:L); impact is availability-only via time delay; no scope change, confidentiality, or integrity effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (TuranSec).

CVSS VectorVendor: TuranSec

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Lifecycle Timeline

Patch available

Aug 11, 2026 - 13:17 EUVD

Analysis Generated

Aug 11, 2026 - 12:30 vuln.today

DescriptionCVE.org

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 borrowers => edit_borrowers permission to cause a time-based denial of service by storing a SQL payload in a patron lang field. The value is concatenated raw into a subquery in Koha::AdditionalContents->search_for_display when an issue slip is printed for the affected patron. The 25-character column length limits exploitation to timing attacks; data extraction is not practical. The stored payload executes on each subsequent issue-slip print, scaling linearly with the SLEEP value and the number of slip-news rows.

AnalysisAI

Stored SQL injection in Koha across all active release branches (24.11, 25.05, 25.11, 26.05) allows authenticated library staff holding the edit_borrowers permission to plant a compact time-based SLEEP payload in a patron's lang field, causing recurring denial-of-service each time an issue slip is printed for that patron. The 25-character column constraint prevents practical data extraction, confining real-world impact strictly to workflow disruption in the circulation slip-printing path. No public exploit code or active exploitation has been identified at time of analysis; the attack requires valid staff credentials scoped to a specific Koha permission.

Technical ContextAI

Koha (CPE: cpe:2.3:a:koha_community:koha) is an open-source Integrated Library System written primarily in Perl, widely deployed by public, academic, and school libraries worldwide. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command): the patron lang field value is concatenated directly and without parameterization into a subquery inside the Perl method Koha::AdditionalContents->search_for_display, which executes during issue-slip generation. Because the underlying database column is defined as VARCHAR(25), only short injectable expressions such as compact SLEEP() or BENCHMARK() calls fit within the constraint, rendering UNION-based data extraction and boolean-based enumeration infeasible. The stored nature of the injection means the payload persists in the database record and fires on every subsequent issue-slip print event for the affected patron, with cumulative delay scaling linearly with the SLEEP argument multiplied by the number of configured slip-news rows.

RemediationAI

Upgrade Koha to the first patched release on the affected branch as documented in Koha Community Bug 42866 at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42866; exact fixed version numbers were not independently confirmed from the available input data and must be obtained from the official Koha release notes at https://koha-community.org/ for each supported branch (24.11, 25.05, 25.11, 26.05). As an immediate compensating control, database administrators can audit the patron lang column for SQL metacharacters - specifically semicolons and the keywords SLEEP and BENCHMARK - and sanitize any affected records. Restricting the borrowers => edit_borrowers permission to the smallest necessary set of trusted staff accounts eliminates the attacker surface; this trade-off is low-impact in most libraries where patron editing is already a limited role. Temporarily suspending issue-slip printing removes the trigger mechanism entirely but disrupts normal circulation workflows and should be treated as a break-glass measure only.