Memphis Documents Library <= 3.1.5 - Arbitrary File Download

Strategic Overview

Status
Patched in 3.1.6
Affected Version
<= 3.1.5
CVSS
7.5High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE pending
View all Memphis Documents Library vulnerabilities

At a glance

This record tracks a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Memphis Documents Library WordPress plugin, affecting versions <= 3.1.5. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 3.1.6; sites on affected versions should update now. Disclosed March 2016, reported by Felipe Molina de la Torre.

Vulnerability Overview

The Memphis Documents Library plugin for WordPress is vulnerable to arbitrary file downloads in versions up to, and including 3.1.5 via the 'mdocs-img-preview' parameter. This makes it possible for unauthenticated users to access and download arbitrary files on the server such as the wp-config.php file which can reveal sensitive information to an attackers.

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.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Memphis Documents Library <= 3.1.5 carries this weakness at mdocs-img-preview, and reaching it takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Memphis Documents Library the fix is 3.1.6: builds <= 3.1.5 are affected, anything from 3.1.6 onward is not.

Remediation

Update to version 3.1.6, 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. None of that substitutes for the fix: Memphis Documents Library 3.1.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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