dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-36058

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The Send Basket functionality in Koha Library before 23.05.10 is susceptible to Time-Based SQL Injection because it fails to sanitize the POST parameter bib_list in /cgi-bin/koha/opac-sendbasket.pl, allowing library users to read arbitrary data from the database.

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

The Send Basket functionality in Koha Library before version 23.05.10 contains a time-based SQL injection vulnerability in /cgi-bin/koha/opac-sendbasket.pl. The POST parameter 'bib_list' is not sanitized before being used in database queries, allowing authenticated library users to inject malicious SQL and read arbitrary data from the database.

MitigationUpgrade to Koha Library version 23.05.10 or later which includes proper sanitization of the bib_list parameter to prevent SQL injection.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Koha Library installation
    Check for Koha installation by looking for the opac-sendbasket.pl file in the web server's CGI directory, typically in /cgi-bin/koha/opac/ or search for 'koha' in web server directories.
    Affected if The opac-sendbasket.pl file exists in the Koha installation directory.
  2. Identify installed Koha version
    Check the Koha version by looking at the VERSION file in the Koha root directory, the package version (dpkg -l | grep koha or rpm -q koha), or by accessing the staff interface about page.
    Affected if The installed version is lower than 23.05.10.
  3. Verify the vulnerable script is accessible
    Confirm opac-sendbasket.pl is accessible via the web server at the opac CGI path (typically /cgi-bin/koha/opac-sendbasket.pl). Check if the web server is configured to serve Koha's opac CGI scripts.
    Affected if The opac-sendbasket.pl script is accessible and running.
  4. Confirm user authentication context
    Determine if the Koha opac (public catalog) is accessible to authenticated library users. The vulnerability requires an authenticated library user session to exploit the bib_list POST parameter.
    Affected if Authenticated user accounts can access the opac and the Send Basket feature.
  5. Check database configuration
    Review the Koha database configuration (typically in koha-conf.xml) to confirm which database backend is in use (MySQL/MariaDB/PostgreSQL). Time-based SQL injection timing varies by database type.
    Affected if Koha uses a vulnerable database backend (MySQL/MariaDB/PostgreSQL) with the opac-sendbasket.pl feature enabled.

If Koha Library is installed with a version lower than 23.05.10, the opac-sendbasket.pl script is accessible, and authenticated users can access the opac Send Basket feature, then the environment is affected by this SQL injection vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Koha Library version 23.05.10 or later which includes proper sanitization of the bib_list parameter to prevent SQL injection.

Recommended fix High confidence

Koha 23.05.10 or later

  1. 1. Backup your current Koha installation and database before attempting any upgrade.
  2. 2. Ensure you have a working test/staging environment to validate the upgrade.
  3. 3. Download Koha version 23.05.10 or later from the official Koha website (koha-community.org) or the official GitHub repository.
  4. 4. Follow the official Koha upgrade documentation for your operating system to install the new version.
  5. 5. Specifically, replace or update the file /cgi-bin/koha/opac-sendbasket.pl with the patched version that sanitizes the bib_list POST parameter.
  6. 6. After upgrade, verify the SQL injection vulnerability is remediated by testing the Send Basket functionality.
  7. 7. Deploy the tested upgrade to production.
Caveat Major version upgrades may introduce breaking changes; test thoroughly in staging before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36058 — 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-2024-36058 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