CVE-2014-8336

WP DB Manager < 2.7.2 - Arbitrary File Read

2014-10-13 00:00
Larry W. Cashdollar

Strategic Overview

Status
Patched in 2.7.2
Affected Plugin
WP-DBManager
Affected Version
< 2.7.2
CVSS
6.5Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2014-8336
View all WP-DBManager vulnerabilities

At a glance

CVE-2014-8336 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP-DBManager WordPress plugin, affecting versions < 2.7.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). The issue is fixed in version 2.7.2; sites on affected versions should update now. Disclosed October 2014, reported by Larry W. Cashdollar.

Vulnerability Overview

The "Sql Run Query" panel in WP-DBManager (aka Database Manager) plugin before 2.7.2 for WordPress allows remote attackers to read arbitrary files by leveraging failure to sufficiently limit queries, as demonstrated by use of LOAD_FILE in an INSERT statement.

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 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')

Reaching this weakness in WP-DBManager < 2.7.2 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 WP-DBManager the fix is 2.7.2: builds < 2.7.2 are affected, anything from 2.7.2 onward is not.

Remediation

Update to version 2.7.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP-DBManager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-DBManager 2.7.2 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