WordPress security by component
Asset CleanUp: Page Speed Booster
Plugin description
Asset CleanUp: Page Speed Booster identifies and disables selected scripts and styles on WordPress pages to manage asset loading.
Asset CleanUp: Page Speed Booster (wp-asset-clean-up) is a WordPress plugin with 7 published CVE records in this archive. The latest tracked vulnerability was published Sep 25, 2026; the highest published CVSS base score is 7.2.
Plugin slug:
wp-asset-clean-upLatest vulnerability
CVE-2026-12037: Asset CleanUp: Page Speed Booster: Server-side request forgery
Asset CleanUp (affected: <= 1.4.0.5). An Administrator or higher can supply page_url to make server-origin requests to arbitrary destinations, including internal services. The SSRF path is reachable only when an administrator has configured dom_get_type as wp_remote_post. The endpoint and response visibility are unspecified.
| Safe version |
|
||
|---|---|---|---|
| Sep 25, 2026 |
CVE-2026-12037
Asset CleanUp: Page Speed Booster: Server-side request forgery
Asset CleanUp (affected: <= 1.4.0.5). An Administrator or higher can supply page_url to make server-origin requests to arbitrary destinations, including internal services. The SSRF path is reachable only when an administrator has configured dom_get_type as wp_remote_post. The endpoint and response visibility are unspecified.
|
See mitigation notes |
CVE5.5
NVDPending
|
| Sep 19, 2026 |
CVE-2026-13354
Asset CleanUp comment content becomes script when CSS combining is enabled
Unauthenticated comment content can become stored script through insufficient sanitization and output escaping when combine_loaded_css is enabled. A user must view affected output for browser execution. The export does not disclose the vulnerable rendering function, precise injected field or whether comment approval is required; it does not establish a moderation bypass. Authoritative affected range: <= 1.4.0.5. No fixed release is confirmed in this review.
|
See mitigation notes |
CVE7.2
NVDPending
|
| Sep 17, 2026 |
CVE-2026-66571
Asset CleanUp: Page Speed Booster permits forged cross-site requests
Asset CleanUp: Page Speed Booster through 1.4.0.5 is affected by CSRF: an attacker needs no account but must induce victim interaction so a request is sent in the victim's browser context. The export does not name the endpoint, action, parameters, required victim role or operation performed. Its CNA vector reports limited confidentiality, integrity and availability impact with a changed scope; it does not establish a particular data disclosure, setting change or destructive action. The affected-version data marks 1.4.0.6 unaffected.
|
1.4.0.6 |
CVE7.1
NVDPending
|
| May 12, 2026 |
CVE-2026-45212
Asset CleanUp: Page Speed Booster: A security weakness
Asset CleanUp: Page Speed Booster is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 1.4.0.3.
|
1.4.0.4 |
CVE5.3
NVDPending
|
| Nov 30, 2024 |
CVE-2024-53738
Asset CleanUp: Page Speed Booster: Server-side request forgery
Asset CleanUp: Page Speed Booster is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.
|
See mitigation notes |
CVE4.4
NVDPending
|
| Nov 01, 2024 |
CVE-2024-43314
Asset CleanUp: Page Speed Booster: A security weakness
Asset CleanUp: Page Speed Booster is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVD8.8
|
| Oct 11, 2022 |
CVE-2021-36899
Asset CleanUp: Page Speed Booster: Cross-site scripting
Asset CleanUp: Page Speed Booster is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.8
NVD4.8
|