dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-36057

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
Koha Library before 23.05.10 fails to sanitize user-controllable filenames prior to unzipping, leading to remote code execution. The line "qx/unzip $filename -d $dirname/;" in upload-cover-image.pl is vulnerable to command injection via shell metacharacters because input data can be controlled by an attacker and is directly included in a system command, i.e., an attack can occur via malicious filenames after uploading a .zip file and clicking Process Images.

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

Koha Library before 23.05.10 contains a command injection vulnerability in upload-cover-image.pl where user-controlled filenames from uploaded ZIP files are passed directly to a system unzip command without sanitization, allowing shell metacharacters in filenames to execute arbitrary commands.

MitigationUpgrade to Koha 23.05.10 or later. Until patched, disable the upload-cover-image.pl script or implement input validation to strip shell metacharacters from filenames before the unzip operation.

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. Identify Koha installation version
    Locate the Koha version file in your installation directory, or access the system administration interface to view the version information
    Affected if The installed version is any version prior to 23.05.10 (e.g., 23.05.09, 23.05.08, earlier releases)
  2. Locate the upload-cover-image.pl script
    Search for the file upload-cover-image.pl in your Koha web directory, typically under the CGI or scripts folder accessible via web
    Affected if The script exists and is present in a publicly accessible location on your web server
  3. Verify script accessibility
    Check if the upload-cover-image.pl script is enabled in your web server configuration and accessible via HTTP/HTTPS requests
    Affected if The script is enabled and reachable over the network, allowing users to upload files
  4. Confirm vulnerable code pattern exists
    Inspect the upload-cover-image.pl source code and locate the section that handles ZIP file extraction using a system unzip command; verify that filenames extracted from the ZIP are used directly in the command without sanitization
    Affected if The code passes ZIP archive member names directly to a system() or exec() call without filtering shell metacharacters
  5. Check if cover image upload feature is in use
    Review your Koha configuration to determine if the cover image upload feature is enabled, or check web server logs for access to upload-cover-image.pl
    Affected if The feature is enabled or has been accessed, indicating potential exposure to the vulnerability

You are affected if your Koha installation version is before 23.05.10 AND the upload-cover-image.pl script exists and is accessible on your web server.

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 23.05.10 or later. Until patched, disable the upload-cover-image.pl script or implement input validation to strip shell metacharacters from filenames before the unzip operation.

Recommended fix High confidence

23.05.10

  1. 1. Backup your existing Koha installation and database before proceeding with any upgrade.
  2. 2. Download Koha 23.05.10 or later from the official Koha website (koha-community.org) or the GitHub repository.
  3. 3. Review the official upgrade documentation for your specific installation method (Debian packages, source install, or Docker).
  4. 4. Stop the Koha web server and related services to prevent access during the upgrade.
  5. 5. Install the new version (23.05.10 or later) following the standard upgrade procedure for your deployment method.
  6. 6. Verify that the upload-cover-image.pl file has been updated and no longer contains the vulnerable qx/unzip command with unsanitized input.
  7. 7. Restart the Koha services and web server.
  8. 8. Test the image upload functionality to confirm the fix works correctly.
Caveat No specific breaking changes mentioned in the provided material; standard upgrade precautions apply (backup, testing in staging recommended).

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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