CVE-2014-10383

Memphis Documents Library <= 2.6.16 - Remote File Inclusion

2015-09-04 00:00
Anonymous

Strategic Overview

Status
Patched in 3.0
Affected Version
< 3.0
CVSS
9.8Critical
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2014-10383
View all Memphis Documents Library vulnerabilities

At a glance

CVE-2014-10383 is a critical-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Memphis Documents Library WordPress plugin, affecting versions < 3.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.0; sites on affected versions should update now. Disclosed September 2015.

Vulnerability Overview

The memphis-documents-library plugin before 3.0 for WordPress has Remote File Inclusion.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Reaching this weakness in Memphis Documents Library < 3.0 takes a caller who can reach the endpoint. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For Memphis Documents Library the fix is 3.0: builds < 3.0 are affected, anything from 3.0 onward is not.

Remediation

Update to version 3.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Memphis Documents Library: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Memphis Documents Library 3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C