dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22954

CRITICAL · 10.0 CVSS v3.1 Published 2025-03-12
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
GetLateOrMissingIssues in C4/Serials.pm in Koha before 24.11.02 allows SQL Injection in /serials/lateissues-export.pl via the supplierid or serialid 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

SQL injection vulnerability in Koha's serials module allows attackers to inject malicious SQL queries via the supplierid or serialid parameters in /serials/lateissues-export.pl. The GetLateOrMissingIssues function in C4/Serials.pm fails to properly sanitize user input before using it in database queries, enabling unauthenticated attackers to access, modify, or delete sensitive library data.

MitigationUpgrade to Koha version 24.11.02 or later which contains the fix for this SQL injection vulnerability. Until then, consider restricting access to /serials/lateissues-export.pl or implementing WAF rules to block SQL injection attempts.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Check Koha version
    Locate the Koha installation and identify the installed version number (typically found in koha-conf.xml, package metadata, or the admin interface)
    Affected if Version is earlier than 24.11.02 (the fix was released in 24.11.02)
  2. Verify serials module is enabled
    Confirm that the serials module is active in the Koha system. Check via admin interface under 'System preferences' or 'Modules' or inspect the permissions table for serial-related privileges
    Affected if The serials module is enabled and accessible to the user
  3. Confirm lateissues-export.pl is accessible
    Attempt to access the URL path /serials/lateissues-export.pl on the Koha server (via HTTP request or check web server configuration)
    Affected if The script is accessible without authentication or with the attacker's user privileges
  4. Check for existing web server restrictions
    Inspect web server configuration (Apache/nginx) or WAF rules for any filters or access controls targeting /serials/lateissues-export.pl or SQL injection patterns
    Affected if No WAF rules or URL filters are blocking the vulnerable endpoint
  5. Review database query logging
    Enable or inspect database query logs for unusual or suspicious SQL queries containing UNION, SELECT, or DROP statements passed through supplierid or serialid parameters to lateissues-export.pl
    Affected if Malicious SQL injection attempts are present in logs

A user is affected if their Koha version is earlier than 24.11.02, the serials module is enabled, and the lateissues-export.pl endpoint is accessible without effective filtering.

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 which contains the fix for this SQL injection vulnerability. Until then, consider restricting access to /serials/lateissues-export.pl or implementing WAF rules to block SQL injection attempts.

Recommended fix Moderate confidence

Koha 24.11.02 or later

  1. Backup the current Koha installation and database before proceeding with any upgrade
  2. Identify the current Koha version by checking the admin interface or running: koha-version --instance <instance_name>
  3. Upgrade Koha to version 24.11.02 or later. For Debian/Ubuntu systems using the Koha packages, run: apt-get update && apt-get install koha-common
  4. Alternatively, for manual installations, download and install the latest release from koha-community.org
  5. After upgrade, verify the version is 24.11.02 or higher: koha-version --instance <instance_name>
  6. Test the /serials/lateissues-export.pl endpoint with the supplierid and serialid parameters to confirm the SQL injection is fixed
  7. Review the Koha 24.11.02 release notes for any required database migrations and run necessary updates
Caveat Review Koha 24.11.x release notes for any breaking changes specific to your installation and test in a staging environment before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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