dbcve.org
KohaApplication

CVE-2014-1925

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-24
Fix available
A fix is available. Upgrade to 3.08.23 / 3.10.13 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
SQL injection vulnerability in the MARC framework import/export function (admin/import_export_framework.pl) in Koha before 3.8.23, 3.10.x before 3.10.13, 3.12.x before 3.12.10, and 3.14.x before 3.14.3 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors. NOTE: this can be leveraged by remote attackers using CVE-2014-1924.

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
How this class of weakness works · CWE-89

User input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.

General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:< 3.08.23>= 3.10.00, < 3.10.13>= 3.12.00, < 3.12.10>= 3.14.00, < 3.14.03

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

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 3.08.23 / 3.10.13 / 3.12.10 or later
Fixed in 3.08.233.10.133.12.10
Recommended fix High confidence

3.08.23, 3.10.13, 3.12.10, or 3.14.03 (depending on your current branch)

  1. 1. Identify the currently installed Koha version by checking the About page in the staff interface or running: koha-version --instance <instance_name>
  2. 2. Determine which version branch you are on (3.08.x, 3.10.x, 3.12.x, or 3.14.x)
  3. 3. Backup the Koha database and configuration files before proceeding with any upgrade
  4. 4. Upgrade to the appropriate fixed version: if on 3.08.x upgrade to 3.08.23; if on 3.10.x upgrade to 3.10.13; if on 3.12.x upgrade to 3.12.10; if on 3.14.x upgrade to 3.14.03
  5. 5. Use the distribution's package manager or compile from source using the specific tagged release from the Koha source repository
  6. 6. Run the database upgrade scripts: koha-upgrade --instance <instance_name>
  7. 7. Verify the upgrade was successful and test the admin/import_export_framework.pl functionality
  8. 8. Ensure the system is fully patched by checking for any other applicable CVEs (note: CVE-2014-1924 is a separate authentication bypass that can be used to leverage this SQL injection)
Caveat Major version upgrades may require database schema changes and testing of custom configurations; review the release notes for your target version before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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