CVE-2014-1626
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 · uneditedXML External Entity (XXE) vulnerability in MARC::File::XML module before 1.0.2 for Perl, as used in Evergreen, Koha, perl4lib, and possibly other products, allows context-dependent attackers to read arbitrary files via a crafted XML file.
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 confidenceXXE vulnerability in MARC::File::XML Perl module versions before 1.0.2 allows attackers to read arbitrary files by crafting malicious XML with external entity references. The vulnerability affects library systems including Evergreen, Koha, and perl4lib.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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<= 1.0.1= 1.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify MARC::File::XML module is installedRun 'perl -MMARC::File::XML -e 'print $MARC::File::XML::VERSION' in your Perl environmentAffected if Module is installed and responds to the version query
-
Determine installed version of MARC::File::XMLCompare the version number from step 1 against the affected range: versions 1.0 and 1.0.1 are vulnerable; version 1.0.2 and later are fixedAffected if Installed version is 1.0.1 or lower, or shows version 1.0 without a patch level
-
Identify applications using this Perl moduleSearch codebase for 'use MARC::File::XML' or 'require MARC::File::XML' statements in your library system applications (Evergreen, Koha, perl4lib projects)Affected if Any application imports or uses MARC::File::XML and the version is vulnerable
-
Check if XML processing with external entities is enabledInspect the Perl code that calls MARC::File::XML for XML::Parser or XML::LibXML configuration; look for settings that allow external entity resolutionAffected if The module processes untrusted XML input with external entity references enabled
-
Verify XML data sources are untrustedReview whether the XML files or data streams processed by this module originate from user input, external APIs, or untrusted sourcesAffected if The module parses XML from untrusted sources without sanitization
Your environment is affected if MARC::File::XML version 1.0.1 or earlier is installed and used to process XML from any source, allowing external entity references to be resolved.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate MARC::File::XML to version 1.0.2 or later, which includes XXE protection by disabling external entity processing. Identify all systems using this module and apply the patch.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1626 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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