CVE-2020-36836

WP Fastest Cache <= 0.9.0.2 - Authenticated (Subscriber+) Arbitrary File Deletion

2020-02-05 00:00
Glyn Wintle

Strategic Overview

Status
Patched in 0.9.0.3
Affected Plugin
WP Fastest Cache – WordPress Cache Plugin
Affected Version
< 0.9.0.3
CVSS
8.0High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2020-36836
View all WP Fastest Cache – WordPress Cache Plugin vulnerabilities

At a glance

CVE-2020-36836 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Fastest Cache WordPress plugin, affecting versions < 0.9.0.3. It carries a CVSS score of 8.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.9.0.3; sites on affected versions should update now. Disclosed February 2020, reported by Glyn Wintle.

Vulnerability Overview

The WP Fastest Cache plugin for WordPress is vulnerable to unauthorized arbitrary file deletion in versions up to, and including, 0.9.0.2 due to a lack of capability checking and insufficient path validation. This makes it possible for authenticated users with minimal permissions to delete arbitrary files from the server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Fastest Cache < 0.9.0.3 takes an account at Subscriber level or above. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Fastest Cache the fix is 0.9.0.3: builds < 0.9.0.3 are affected, anything from 0.9.0.3 onward is not.

Remediation

Update to version 0.9.0.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Fastest Cache 0.9.0.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-36836https://www.wordfence.com/threat-intel/vulnerabilities/id/82f80916-37ab-4c5a-9787-2544c620acachttps://nvd.nist.gov/vuln/detail/CVE-2020-36836

Related records

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