dbcve.org
KohaApplication

CVE-2026-31844

HIGH · 8.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 24.11.12 / 25.05.07 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An authenticated SQL Injection vulnerability (CWE-89) exists in the Koha staff interface in the /cgi-bin/koha/suggestion/suggestion.pl endpoint due to improper validation of the displayby parameter used by the GetDistinctValues functionality. Successful exploitation may lead to full compromise of the backend database, including disclosure or modification of stored data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An authenticated SQL injection vulnerability exists in Koha library management system's staff interface at /cgi-bin/koha/suggestion/suggestion.pl. The displayby parameter passed to GetDistinctValues functionality lacks proper validation, allowing a low-privileged staff user to inject arbitrary SQL commands through crafted requests, potentially exposing or modifying the entire database.

MitigationImplement strict input validation on the displayby parameter and refactor the GetDistinctValues functionality to use parameterized queries or prepared statements instead of dynamic SQL construction. Apply available vendor patches for Koha.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KohaApplication
Affected:>= 24.11.0, < 24.11.12>= 25.05.0, < 25.05.07= 25.11.00

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Koha version
    Locate the Koha installation and check its version number, typically found in the admin interface under 'About Koha' or in version configuration files within the Koha directory structure
    Affected if The installed version falls within >= 24.11.0, < 24.11.12; >= 25.05.0, < 25.05.07; or = 25.11.00
  2. Verify staff interface is accessible
    Confirm that the Koha staff interface at /cgi-bin/koha/ is accessible and operational for your installation
    Affected if The staff interface is enabled and reachable, which is required for authentication to exploit this vulnerability
  3. Confirm suggestion module is enabled
    Check if the suggestion.pl module is available and enabled in your Koha installation, typically through the staff interface or system preferences
    Affected if The suggestion module is enabled and accessible to staff users, exposing the vulnerable GetDistinctValues functionality
  4. Identify if low-privilege staff accounts exist
    Review user accounts in Koha to determine if any staff-level users exist with access to the suggestion feature
    Affected if Low-privileged staff user accounts exist with access to the suggestion.pl endpoint

Your environment is affected if you are running an affected Koha version (24.11.x before 24.11.12, 25.05.x before 25.05.07, or 25.11.00) with the staff interface and suggestion module enabled and accessible to staff users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.11.12 / 25.05.07 or later
Fixed in 24.11.1225.05.07
Interim mitigation

Implement strict input validation on the displayby parameter and refactor the GetDistinctValues functionality to use parameterized queries or prepared statements instead of dynamic SQL construction. Apply available vendor patches for Koha.

Recommended fix High confidence

24.11.12, 25.05.07, or 25.11.01+

  1. Backup the Koha database and configuration files before upgrading
  2. Ensure you have a tested restore procedure
  3. Upgrade Koha to version 24.11.12 (for 24.11.x installations)
  4. OR upgrade to version 25.05.07 (for 25.05.x installations)
  5. OR upgrade to version 25.11.01 or later (for 25.11.x installations)
  6. Run the database upgrade scripts if required (koha-upgrade script)
  7. Verify the upgrade was successful by logging into the staff interface
  8. Test the /cgi-bin/koha/suggestion/suggestion.pl endpoint to confirm functionality
Caveat Koha upgrades may include database schema changes; review release notes for any breaking changes before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Koha Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31844 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data