CVE-2015-5468

WP eCommerce Shop Styling < 2.6 - Directory Traversal

2015-07-05 00:00
Larry W. Cashdollar

Strategic Overview

Status
Patched in 2.6
Affected Version
< 2.6
CVSS
7.5High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2015-5468
View all WP eCommerce Shop Styling vulnerabilities

At a glance

CVE-2015-5468 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP eCommerce Shop Styling WordPress plugin, affecting versions < 2.6. 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 2.6; sites on affected versions should update now. Disclosed July 2015, reported by Larry W. Cashdollar.

Vulnerability Overview

Directory traversal vulnerability in the WP e-Commerce Shop Styling plugin before 2.6 for WordPress allows remote attackers to read arbitrary files via a .. (dot dot) in the filename parameter to includes/download.php.

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

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

Remediation

Update to version 2.6, or a newer patched version

How does WordSec protect against this?

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