Koha Community up to 26.05.2 Reports cat_issues_top.pl calculate criteria/filter/limit sql injection

Summaryinfo

A vulnerability was found in Koha Community Koha up to 24.10.x/24.11.18/25.05.13/25.11.7/26.05.2. It has been classified as critical. This issue affects the function calculate of the file reports/cat_issues_top.pl of the component Reports Module. Performing a manipulation of the argument criteria/filter/limit results in sql injection. This vulnerability is known as CVE-2026-105107. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in Koha Community Koha up to 24.10.x/24.11.18/25.05.13/25.11.7/26.05.2. This affects the function calculate of the file reports/cat_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. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Koha is vulnerable to SQL injection in the Most-circulated items report. The reports/cat_issues_top.pl script (sub calculate) concatenates the user-controlled Criteria, Filter, and Limit request parameters directly into dynamic SQL. Criteria is only prefix-normalized and never validated against an allow-list, so it is inserted verbatim into identifier positions (SELECT DISTINCTROW, GROUP BY, ORDER BY, and the main calculation query). Filter values are concatenated raw into single-quoted LIKE, BETWEEN, and comparison fragments. Limit is appended raw to a LIMIT clause. An authenticated staff user with the reports module permission (not requiring superlibrarian) can inject arbitrary SQL and read any table reachable by the Koha database user, including borrowers (userid and bcrypt password hashes, two-factor secrets, personal data), api_keys, and sessions. The issue is fixed in Koha 24.11.19, 25.05.14, 25.11.08, and 26.05.03, and in the 26.11 development branch. This is the unpatched twin of reports/bor_issues_top.pl (CVE-2026-70372).

The advisory is shared at bugs.koha-community.org. This vulnerability is uniquely identified as CVE-2026-105107 since 10/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 24.11.19, 25.05.14, 25.11.08 or 26.05.03 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Koha Community

Name

• Koha

Version

• 24.0
• 24.1
• 24.2
• 24.3
• 24.4
• 24.5
• 24.6
• 24.7
• 24.8
• 24.9
• 24.10
• 24.11.0
• 24.11.1
• 24.11.2
• 24.11.3
• 24.11.4
• 24.11.5
• 24.11.6
• 24.11.7
• 24.11.8
• 24.11.9
• 24.11.10
• 24.11.11
• 24.11.12
• 24.11.13
• 24.11.14
• 24.11.15
• 24.11.16
• 24.11.17
• 24.11.18
• 25.05.0
• 25.05.1
• 25.05.2
• 25.05.3
• 25.05.4
• 25.05.5
• 25.05.6
• 25.05.7
• 25.05.8
• 25.05.9
• 25.05.10
• 25.05.11
• 25.05.12
• 25.05.13
• 25.11.0
• 25.11.1
• 25.11.2
• 25.11.3
• 25.11.4
• 25.11.5
• 25.11.6
• 25.11.7
• 26.05.0
• 26.05.1
• 26.05.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion