WP Super Cache <= 1.4.4 - Authenticated File Deletion

2015-09-25 00:00
Anonymous

Strategic Overview

Status
Patched in 1.4.5
Affected Plugin
WP Super Cache
Affected Version
< 1.4.5
CVSS
5.4Medium
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE pending
View all WP Super Cache vulnerabilities

At a glance

This record tracks a medium-severity Improper Input Validation vulnerability in the WP Super Cache WordPress plugin, affecting versions < 1.4.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 1.4.5; sites on affected versions should update now. Disclosed September 2015.

Vulnerability Overview

The WP Super Cache plugin for WordPress is vulnerable to Authenticated File Deletion in versions up to, and including, 1.4.4. Code that sanitized directory paths when deleting cache files wasn't secure and might allow an attacker to view or delete files named index.html. This makes it possible for authenticated attackers to delete some index files, which can lead to some site accessibility issues and information disclosure.

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.

CWE-20: Improper Input Validation

Reaching this weakness in WP Super Cache < 1.4.5 takes any authenticated account. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For WP Super Cache the fix is 1.4.5: builds < 1.4.5 are affected, anything from 1.4.5 onward is not.

Remediation

Update to version 1.4.5, or a newer patched version

How does WordSec protect against this?

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