CVE-2021-24209

WP Super Cache <= 1.7.1 - Authenticated (Admin+) Remote Code Execution

2021-03-16 00:00
R3N0

Strategic Overview

Status
Patched in 1.7.2
Affected Plugin
WP Super Cache
Affected Version
< 1.7.2
CVSS
7.2High
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2021-24209
View all WP Super Cache vulnerabilities

At a glance

CVE-2021-24209 is a high-severity Improper Input Validation vulnerability in the WP Super Cache WordPress plugin, affecting versions < 1.7.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.7.2; sites on affected versions should update now. Disclosed March 2021, reported by R3N0.

Vulnerability Overview

The WP Super Cache WordPress plugin before 1.7.2 was affected by an authenticated (admin+) RCE in the settings page due to input validation failure and weak $cache_path check in the WP Super Cache Settings -> Cache Location option. Direct access to the wp-cache-config.php file is not prohibited, so this vulnerability can be exploited for a web shell injection.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-20: Improper Input Validation

Reaching this weakness in WP Super Cache < 1.7.2 takes an account at Admin level or above. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For WP Super Cache the fix is 1.7.2: builds < 1.7.2 are affected, anything from 1.7.2 onward is not.

Remediation

Update to version 1.7.2, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin 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 Super Cache 1.7.2 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