CVE-2019-13635

WP Fastest Cache <= 0.8.9.5 - Directory Traversal

2019-07-28 00:00
Imre Rad

Strategic Overview

Status
Patched in 0.8.9.6
Affected Version
<= 0.8.9.5
CVSS
9.1Critical
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2019-13635
View all WP Fastest Cache – WordPress Cache Plugin vulnerabilities

At a glance

CVE-2019-13635 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP Fastest Cache WordPress plugin, affecting versions <= 0.8.9.5. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 0.8.9.6; sites on affected versions should update now. Disclosed July 2019, reported by Imre Rad.

Vulnerability Overview

The WP Fastest Cache plugin through 0.8.9.5 for WordPress allows wpFastestCache.php and inc/cache.php Directory Traversal.

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.

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

Reaching this weakness in WP Fastest Cache <= 0.8.9.5 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 Fastest Cache the fix is 0.8.9.6: builds <= 0.8.9.5 are affected, anything from 0.8.9.6 onward is not.

Remediation

Update to version 0.8.9.6, or a newer patched version

How does WordSec protect against this?

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