CVE-2026-70373 Koha Community CVE debrief

Who should care

Koha administrators, librarians with staff access, and IT personnel responsible for Koha installations should be aware of this vulnerability and take immediate action to mitigate the risk. They should review access controls, monitor database activity, and ensure proper input validation and sanitization are in place to prevent SQL injection attacks.

Technical summary

The circulation statistics report in Koha, specifically the issues_stats.pl script, constructs SQL queries by concatenating user-controlled request parameters without proper sanitization. This allows an authenticated staff user with reports module permission to inject arbitrary SQL and potentially read any table accessible by the Koha database user, including sensitive information such as borrower data, API keys, and session information. To mitigate, verify and restrict report module access, monitor for suspicious queries, and implement input validation.

Defensive priority

Authenticated staff users with reports module permissions may be able to inject SQL; verify and restrict report module access, monitor for suspicious queries.

Recommended defensive actions

• Restrict access to the reports module to only necessary personnel
• Monitor database queries for suspicious activity
• Implement input validation and sanitization for user-controlled parameters
• Consider using prepared statements with parameterized queries
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The circulation statistics report in Koha uses user-controlled parameters to construct SQL queries without proper sanitization, allowing for potential SQL injection attacks. An authenticated staff user with reports module permission could inject arbitrary SQL and read any table accessible by the Koha database user. To verify, defenders should review database query logs for suspicious activity and monitor for unauthorized access to sensitive information.

Official resources