dbcve.org
I\, LibrarianApplication · Scilico

CVE-2018-1000124

CRITICAL · 10.0 CVSS v3.1 Published 2018-03-13
Fix available
A fix is available. Upgrade to after 4.8 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
I Librarian I-librarian version 4.8 and earlier contains a XML External Entity (XXE) vulnerability in line 154 of importmetadata.php(simplexml_load_string) that can result in an attacker reading the contents of a file and SSRF. This attack appear to be exploitable via posting xml in the Parameter form_import_textarea.

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

I Librarian versions 4.8 and earlier contains an XXE vulnerability in importmetadata.php at line 154 where simplexml_load_string processes XML input from the form_import_textarea parameter without disabling external entity processing. Attackers can exploit this to read arbitrary local files from the server filesystem and perform SSRF attacks against internal network resources.

MitigationFix requires configuring libxml_disable_entity_loader(true) before XML parsing calls and/or implementing strict input validation/whitelisting to prevent malicious entity declarations. Also audit other XML parsing locations for similar XXE vulnerabilities.

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
I\, LibrarianApplication
Affected:<= 4.8

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. Identify the installed version of Scilico I Librarian
    Locate the version file or header in the Scilico I Librarian installation directory (typically in a version.php, about.php, or configuration file). Read the version number and compare it to 4.8
    Affected if The installed version is 4.8 or earlier
  2. Locate the vulnerable importmetadata.php file
    Search the web root or application directory for the file importmetadata.php - typically found in an admin, manage, or import folder
    Affected if The file importmetadata.php exists in the application
  3. Inspect the XML parsing code in importmetadata.php
    Open importmetadata.php and navigate to or around line 154. Look for the simplexml_load_string function call that processes the form_import_textarea parameter
    Affected if The code contains simplexml_load_string processing the form_import_textarea parameter without libxml_disable_entity_loader(true) called beforehand
  4. Check for XXE protection in XML handling
    Search the importmetadata.php file for libxml_disable_entity_loader(true) or LIBXML_NOENT constant used with simplexml_load_string. Also check for any entitywhitelist or DTD restriction configuration
    Affected if No XXE protection is found - simplexml_load_string is called without disabling external entities
  5. Determine if the XML import feature is accessible
    Check if the importmetadata.php endpoint is accessible via web request (GET/POST to the importmetadata.php URL). Verify that the form_import_textarea parameter is accepted
    Affected if The XML import functionality is active and accepts input through the form_import_textarea parameter

You are affected if Scilico I Librarian version is 4.8 or earlier AND importmetadata.php contains simplexml_load_string processing form_import_textarea without XXE protection (libxml_disable_entity_loader) in place.

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.

From vendor data
Upgrade available Upgrade to a release after 4.8
Interim mitigation

Fix requires configuring libxml_disable_entity_loader(true) before XML parsing calls and/or implementing strict input validation/whitelisting to prevent malicious entity declarations. Also audit other XML parsing locations for similar XXE vulnerabilities.

Fix this in I\, Librarian Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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