Koha Community up to 24.11.16/25.05.11/25.11.5/26.05.0 Reports bor_issues_top.pl calculate Criteria/Filter/Limit sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.5$0-$5k3.84

Summaryinfo

A vulnerability was found in Koha Community Koha up to 24.11.16/25.05.11/25.11.5/26.05.0. It has been rated as problematic. Impacted is the function calculate of the file reports/bor_issues_top.pl of the component Reports Module. This manipulation of the argument Criteria/Filter/Limit causes sql injection. The identification of this vulnerability is CVE-2026-70372. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Koha Community Koha up to 24.11.16/25.05.11/25.11.5/26.05.0. It has been declared as problematic. Affected by this vulnerability is the function calculate of the file reports/bor_issues_top.pl of the component Reports Module. The manipulation of the argument Criteria/Filter/Limit with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at bugs.koha-community.org. This vulnerability is known as CVE-2026-70372 since 08/04/2026. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

Upgrading to version 24.11.17, 25.05.12, 25.11.06 or 26.05.01 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-52674). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.7
VulDB Meta Temp Score: 4.5

VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Koha 24.11.17/25.05.12/25.11.06/26.05.01

Timelineinfo

08/04/2026 Advisory disclosed
08/04/2026 +0 days CVE reserved
08/04/2026 +0 days VulDB entry created
08/04/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: bugs.koha-community.org
Status: Confirmed

CVE: CVE-2026-70372 (🔒)
GCVE (CVE): GCVE-0-2026-70372
GCVE (VulDB): GCVE-100-385819
EUVD: 🔒

Entryinfo

Created: 08/04/2026 15:34
Updated: 08/04/2026 16:48
Changes: 08/04/2026 15:34 (59), 08/04/2026 16:48 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!