CVE-2021-24870

WP Fastest Cache < 0.9.5 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2021-10-14 00:00
Marc-Alexandre Montpas

Strategic Overview

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

At a glance

CVE-2021-24870 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Fastest Cache WordPress plugin, affecting versions < 0.9.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.9.5; sites on affected versions should update now. Disclosed October 2021, reported by Marc-Alexandre Montpas.

Vulnerability Overview

The WP Fastest Cache plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions before 0.9.5. This is due to missing or incorrect nonce validation on the wpfc_save_cdn_integration function. This makes it possible for unauthenticated attackers to perform stored cross-site scripting attacks via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.9.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.9.5: builds < 0.9.5 are affected, anything from 0.9.5 onward is not.

Remediation

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24870https://www.wordfence.com/threat-intel/vulnerabilities/id/372a4550-c38e-46d6-b7f2-15e05708d128https://nvd.nist.gov/vuln/detail/CVE-2021-24870

Related records

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