CVE-2018-17584

WP Fastest Cache <= 0.8.8.5 - Cross-Site Request Forgery via page to wpfastestcacheoptions

2018-10-09 00:00
Mohammed Ansari

Strategic Overview

Status
Patched in 0.8.8.6
Affected Version
<= 0.8.8.5
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2018-17584
View all WP Fastest Cache – WordPress Cache Plugin vulnerabilities

At a glance

CVE-2018-17584 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Fastest Cache WordPress plugin, affecting versions <= 0.8.8.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 0.8.8.6; sites on affected versions should update now. Disclosed October 2018, reported by Mohammed Ansari.

Vulnerability Overview

The WP Fastest Cache plugin 0.8.8.5 for WordPress has CSRF via the wp-admin/admin.php wpfastestcacheoptions page.

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. 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.8.8.5 takes a caller who can reach the endpoint. 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.8.8.6: builds <= 0.8.8.5 are affected, anything from 0.8.8.6 onward is not.

Remediation

Update to version 0.8.8.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.8.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