dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-30076

HIGH · 7.7 CVSS v3.1 Published 2025-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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
Koha before 24.11.02 allows admins to execute arbitrary commands via shell metacharacters in the tools/scheduler.pl report parameter.

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 before 24.11.02 contains a command injection vulnerability in tools/scheduler.pl where the report parameter fails to properly sanitize shell metacharacters, allowing authenticated administrators to execute arbitrary system commands on the host.

MitigationUpgrade to Koha version 24.11.02 or later to patch the command injection vulnerability. Until upgraded, restrict admin access to trusted users only.

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

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

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 version file (usually koha-conf.xml or a VERSION file in the Koha installation directory), or run 'koha-version' if available, or check the admin interface system preferences for the version number
    Affected if The installed version is any version before 24.11.02 (e.g., 24.11.01, 24.05.x, earlier releases)
  2. Verify tools/scheduler.pl exists
    Check if the file 'tools/scheduler.pl' exists within the Koha web directory (typically in /cgi-bin/koha/tools/ or /cgi-bin/koha/)
    Affected if The file exists in the installation and the version is vulnerable
  3. Confirm administrator account access
    Check for existing administrator-level user accounts in Koha (look in the borrowers table with flags like 'superlibrarian' or in the admin interface under Patrons > Administrators)
    Affected if Any administrator or superlibrarian account exists in the system, as the vulnerability requires authenticated admin access to be exploitable
  4. Check if tools module is enabled
    Inspect Koha system preferences or configuration (koha-conf.xml) to determine if the 'tools' module is enabled and accessible
    Affected if The tools module is enabled and accessible to administrators

A user is affected if their Koha installation version is before 24.11.02, the tools/scheduler.pl file exists, and they have administrator-level access to the system.

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 version 24.11.02 or later to patch the command injection vulnerability. Until upgraded, restrict admin access to trusted users only.

Recommended fix High confidence

Koha 24.11.02 or later

  1. 1. Identify the current Koha version by checking the admin interface or using the command: dpkg -l | grep koha-common or rpm -qa | grep koha
  2. 2. If the current version is before 24.11.02, upgrade to version 24.11.02 or later. For Debian/Ubuntu systems, typically: apt-get update && apt-get install koha-common or use the distribution's package manager
  3. 3. For source installations, download the latest release from github.com/koha-community/koha (tagged release 24.11.02 or newer) and follow upgrade documentation
  4. 4. After upgrade, verify the tools/scheduler.pl page is accessible and the vulnerability is fixed by attempting to use shell metacharacters in the report parameter (this should no longer execute commands)
  5. 5. Review Koha release notes for 24.11.02 to confirm security fixes applied
Caveat Review release notes for 24.11.x series for any database schema changes or configuration updates that may require attention during upgrade

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-2025-30076 — 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-2025-30076 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