CVE-2015-4089

WP Fastest Cache < 0.8.3.5 - Multiple Cross-Site Request Forgery

2015-05-26 00:00
Kevin Falcoz

Strategic Overview

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

At a glance

CVE-2015-4089 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Fastest Cache WordPress plugin, affecting versions < 0.8.3.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.3.5; sites on affected versions should update now. Disclosed May 2015, reported by Kevin Falcoz.

Vulnerability Overview

Multiple cross-site request forgery (CSRF) vulnerabilities in the optionsPageRequest function in admin.php in WP Fastest Cache plugin before 0.8.3.5 for WordPress allow remote attackers to hijack the authentication of unspecified victims for requests that call the (1) saveOption, (2) deleteCache, (3) deleteCssAndJsCache, or (4) addCacheTimeout method via the wpFastestCachePage parameter in the 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.3.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.3.5: builds < 0.8.3.5 are affected, anything from 0.8.3.5 onward is not.

Remediation

Update to version 0.8.3.5, 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.3.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2015-4089https://www.wordfence.com/threat-intel/vulnerabilities/id/df32e1d0-3645-432c-a2e4-2d63709c4ffdhttps://nvd.nist.gov/vuln/detail/CVE-2015-4089

Related records

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