CVE-2026-72610: Koha · SQL Injection
Affects KohaSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium · fixed in 26.05.02 : update Koha when convenient.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.05.02, 25.11.07, 25.05.13 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade Koha to 26.05.02, 25.11.07, 25.05.13 or 24.11.18.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Koha CommunityKoha | Affected
| Fixed in
|
| Koha CommunityKoha | Affected
| Fixed in
|
| Koha CommunityKoha | Affected
| Fixed in
|
| Koha CommunityKoha | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict or review staff permissions to limit who can edit borrower information, especially the language field. Monitor for unusual delays during issue slip printing as a potential indicator of exploitation.
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 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.