dbcve.org
Memphis Documents LibraryWordPress extension · Memphis Documents Library Project

CVE-2014-10383

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 3.0 or later.
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
The memphis-documents-library plugin before 3.0 for WordPress has Remote File Inclusion.

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

The memphis-documents-library WordPress plugin before version 3.0 contains a Remote File Inclusion (RFI) vulnerability, likely due to unsanitized user input being used in include/require statements. This critical flaw allows remote attackers to inject and execute arbitrary PHP code from external malicious servers, potentially leading to complete site compromise.

MitigationUpdate the memphis-documents-library plugin to version 3.0 or later. If immediate update is not possible, deactivate and remove the plugin. Audit the system for indicators of compromise, as RFI vulnerabilities are frequently exploited for remote code execution.

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
Memphis Documents LibraryWordPress extension
Affected:< 3.0

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.0/AV:N/AC:L/PR:N/UI:N/S:U/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 if Memphis Documents Library plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'memphis-documents-library' or 'memphis-documents-library-lite'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to see if Memphis Documents Library appears in the list.
    Affected if The plugin folder or listing exists in the WordPress installation.
  2. Determine the installed plugin version
    If the plugin is installed, locate the main plugin PHP file (typically in the plugin root folder) and inspect the plugin header comment which usually contains the Version field. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' entry.
    Affected if The version displayed is below 3.0 (for example, 2.9, 2.8, 1.x, etc.) or if no version is found in the plugin files.
  3. Verify if the plugin is active
    In the WordPress admin dashboard under Plugins > Installed Plugins, check whether Memphis Documents Library shows as 'Active' (the plugin may also be listed as 'Network Active' if using WordPress Multisite).
    Affected if The plugin status shows as Active or Network Active.
  4. Inspect for suspicious remote includes in plugin code
    Examine PHP files within the memphis-documents-library folder, specifically looking for include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without proper sanitization. Search for patterns like 'include($_REQUEST' or 'require($' in the code.
    Affected if Such unsafe include/require patterns exist in the plugin code.

A WordPress installation is affected if the Memphis Documents Library plugin is installed with a version lower than 3.0 and the plugin is currently active, as the vulnerable include statements would be reachable.

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
Upgrade available Upgrade to 3.0 or later
Fixed in 3.0
Interim mitigation

Update the memphis-documents-library plugin to version 3.0 or later. If immediate update is not possible, deactivate and remove the plugin. Audit the system for indicators of compromise, as RFI vulnerabilities are frequently exploited for remote code execution.

Recommended fix Moderate confidence

3.0

  1. 1. Backup your WordPress site (database and files) before making any changes
  2. 2. Navigate to Dashboard > Plugins in WordPress admin panel
  3. 3. Locate Memphis Documents Library in the installed plugins list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.0 or later
  5. 5. If no update appears, deactivate the current version and install version 3.0 from the WordPress plugin repository
  6. 6. After updating, verify the plugin is functioning correctly
  7. 7. Confirm the vulnerability is remediated by checking that the plugin version is 3.0 or higher

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

Fix this in Memphis Documents Library Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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