Security readout for executives and security teams
Plain-English summary
This CVE affects the WP Super Cache WordPress plugin before version 1.7.3. An authenticated user could abuse several plugin settings fields to cause remote code execution. That means a compromised or malicious privileged account could potentially turn a WordPress administration issue into server-side code execution.
Executive priority
Treat as high priority for internet-facing WordPress sites because authenticated RCE can create serious business impact after account compromise. Prioritize sites running old plugin versions or with broad administrator access.
Technical view
The issue is CWE-94 in WP Super Cache settings handling. Several configuration parameters accepted '$' and newline input in a way that could lead to RCE. The record describes this as an incomplete fix for CVE-2021-24209 and indicates versions before 1.7.3 are affected.
Likely exposure
Exposure is likely limited to WordPress sites running WP Super Cache before 1.7.3, especially where authenticated users can access plugin settings. The source bundle does not define exact role requirements.
Exploitation context
The source bundle describes authenticated remote code execution, but does not cite active exploitation. CISA KEV status is false, so there is no provided evidence of known exploited-in-the-wild activity.
Researcher notes
Evidence is concise and version-focused. The record names affected settings parameters but does not provide CVSS, exact role prerequisites, exploit telemetry, or detailed fix mechanics. Avoid assuming unauthenticated reachability.
Mitigation direction
- Upgrade WP Super Cache to version 1.7.3 or later.
- Review vendor and WPScan guidance for current remediation details.
- Restrict WordPress admin and plugin settings access to trusted administrators.
- Audit recently changed plugin settings on affected sites.
Validation and detection
- Inventory WordPress sites using WP Super Cache.
- Confirm installed WP Super Cache versions are 1.7.3 or later.
- Review user accounts with plugin configuration privileges.
- Check logs for suspicious authenticated settings changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-24312 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/2142c3d3-9a7f-4e3c-8776-d469a355d62fCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.