Security readout for executives and security teams
Plain-English summary
A WordPress performance plugin could write unvalidated administrator-controlled settings into a PHP file. If an attacker already has administrator-level access, this could turn plugin configuration into server-side code execution. The source bundle does not show public active exploitation or a CVSS score.
Executive priority
Prioritize internet-facing WordPress sites where administrator accounts may be shared, weakly protected, or externally managed. This is not shown as actively exploited, but admin-level RCE can become serious after credential compromise.
Technical view
CVE-2021-24430 is a CWE-94 issue in Speed Booster Pack PageSpeed Optimization Suite before 4.2.0. The plugin failed to validate caching_exclude_urls and caching_include_query_strings before outputting them into a PHP file, creating authenticated admin+ RCE potential.
Likely exposure
Exposure is limited to WordPress sites using the named Speed Booster Pack plugin versions described as before 4.2.0 or 4.2.0-beta. Exploitation requires administrator-level authentication, so compromised admin accounts are the main practical risk.
Exploitation context
The source bundle lists KEV as false and provides no evidence of active exploitation. Public references describe the issue as authenticated admin+ RCE, not unauthenticated compromise. Treat exploit status as unconfirmed beyond disclosed technical advisories.
Researcher notes
The source data is sparse and internally cautious: severity and CVSS are absent, KEV is false, and the affected version wording includes both before 4.2.0 and 4.2.0-beta references. Avoid claiming unauthenticated exposure or confirmed exploitation.
Mitigation direction
- Inventory WordPress sites for the Speed Booster Pack plugin and version.
- Move off affected versions according to vendor or WPScan guidance.
- Remove the plugin if it is unused or unsupported.
- Restrict and audit WordPress administrator accounts.
- Review recent plugin settings changes and unexpected PHP file modifications.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record installed plugin version and compare with cited affected range.
- Check WordPress admin account list for unknown or unnecessary administrators.
- Review file integrity alerts for unexpected PHP changes.
- Verify remediation against vendor or WPScan guidance before closing.
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-24430 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/945d6d2e-fa25-42c0-a7b4-b1794732a0dfCVE reference · x_refsource_MISC
- https://m0ze.ru/vulnerability/%5B2021-05-10%5D-%5BWordPress%5D-%5BCWE-94%5D-Speed-Booster-Pack-WordPress-Plugin-v4.2.0-beta.txtCVE reference · x_refsource_MISC
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.