CVE-2021-24452

W3 Total Cache <= 2.1.4 - Reflected Cross-Site Scripting via extension

2021-06-28 00:00
Anonymous

Strategic Overview

Status
Patched in 2.1.5
Affected Plugin
W3 Total Cache
Affected Version
0.5 – 2.1.4
CVSS
7.2High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24452
View all W3 Total Cache vulnerabilities

At a glance

CVE-2021-24452 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the W3 Total Cache WordPress plugin, affecting versions 0.5 – 2.1.4. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.5; sites on affected versions should update now. Disclosed June 2021.

Vulnerability Overview

The W3 Total Cache WordPress plugin before 2.1.5 was affected by a reflected Cross-Site Scripting (XSS) issue within the "extension" parameter in the Extensions dashboard, when the 'Anonymously track usage to improve product quality' setting is enabled, as the parameter is output in a JavaScript context without proper escaping. This could allow an attacker, who can convince an authenticated admin into clicking a link, to run malicious JavaScript within the user's web browser, which could lead to full site compromise.

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.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

W3 Total Cache 0.5 – 2.1.4 carries this weakness at extension, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For W3 Total Cache the fix is 2.1.5: builds 0.5 – 2.1.4 are affected, anything from 2.1.5 onward is not.

Remediation

Update to version 2.1.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to W3 Total Cache: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: W3 Total Cache 2.1.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-24452https://www.wordfence.com/threat-intel/vulnerabilities/id/f4d421df-310b-4a83-b521-c0d00045df52https://nvd.nist.gov/vuln/detail/CVE-2021-24452

Related records

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