SQL Injection in Koha Library Reports Module

Koha's reports/bor_issues_top.pl builds dynamic SQL in sub calculate by concatenating several user-controlled request parameters directly into the query string. The Criteria parameter is only normalized by a table-name prefix and is never whitelisted, landing verbatim in identifier positions (SELECT DISTINCTROW, GROUP BY, ORDER BY); Filter values are concatenated raw into single-quoted LIKE, BETWEEN, and comparison fragments, and the Limit parameter is appended raw to a LIMIT clause. An authenticated staff user holding the reports module permission can inject arbitrary SQL and read any table reachable by the Koha database user, including borrowers (password hashes, two-factor secrets, personal data), api_keys, and sessions.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Koha's reports/bor_issues_top.pl contains a critical SQL injection vulnerability where user-controlled parameters are concatenated directly into dynamic SQL queries without proper sanitization. The Criteria parameter bypasses validation entirely and lands in identifier positions (SELECT DISTINCTROW, GROUP BY, ORDER BY), while Filter and Limit parameters are appended raw into LIKE, BETWEEN, and LIMIT clauses. This allows authenticated attackers to inject arbitrary SQL commands, potentially exfiltrating sensitive patron data, circulation records, or administrative information from the underlying database. Libraries using Koha for reporting and analytics face direct risk to patron privacy and operational integrity.

Casky's 322 matching skills leverage Claude's extended reasoning to detect the attack patterns mapped to MITRE TA0001 (Reconnaissance) and TA0043 (Reconnaissance) by identifying SQL injection attempts in request parameters and query construction patterns. Practitioners would observe findings that flag unsanitized parameter concatenation in code paths, detect anomalous SQL syntax in Filter/Limit/Criteria values, and identify attempts to manipulate query structure through identifier injection. The platform's skill mapping correlates these indicators to SQL injection exploitation techniques, enabling security teams to distinguish legitimate reporting queries from injected payloads and prioritize remediation of the dynamic query construction logic in affected report modules.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-70372.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-70372

Casky has 322 skills that investigate the attack patterns behind CVE-2026-70372. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn