Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-6428 high CVSS 7.6

SQL Injection in Koha Community Koha (CVE-2026-6428)

Summary

SQL injection in Koha Community Koha (CVE-2026-6428). Confidential information can be exposed externally. Exploitable via GET /cgi-bin/koha/reports/catalogue_out.pl.

Original description

The description as published by the source.

SQL Injection in reports/catalogue_out.pl in Koha Community Koha through 22.11.37, 23.x, 24.x before 24.11.16, 25.05.x before 25.05.11, 25.11.x before 25.11.05, 26.05.x before 26.05.01, and 26.11.x before 26.11.00 allows an authenticated staff user with the Reports module flag to read arbitrary data from the Koha application database via the Filter URL parameter when the Criteria parameter matches /branchcode/.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-6428 has been found in Koha Community Koha.
Attackers can target a specific entry point like GET /cgi-bin/koha/reports/catalogue_out.pl over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Koha Community Koha CVE-2026-6428" on the vendor's site.

CVE-2026-6428 (Koha Community Koha) — CWE-89 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /cgi-bin/koha/reports/catalogue_out.pl
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in Koha Community Koha. Attackers reach the vulnerable code path via GET /cgi-bin/koha/reports/catalogue_out.pl.

📍 Affected scope

Check the vendor advisory for the affected versions of Koha Community Koha. Attack surface: GET /cgi-bin/koha/reports/catalogue_out.pl.

🔥 Severity

Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /cgi-bin/koha/reports/catalogue_out.pl requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Koha Community Koha を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /cgi-bin/koha/reports/catalogue_out.pl' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /cgi-bin/koha/reports/catalogue_out.pl への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against GET /cgi-bin/koha/reports/catalogue_out.pl on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details