WordPress security by component
Asset CleanUp: Page Speed Booster
Plugin description
Asset CleanUp: Page Speed Booster is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published May 12, 2026; the highest CVE/CNA score is 5.3.
Plugin slug:
wp-asset-clean-upLatest vulnerability
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.
| Safe version |
|
||
|---|---|---|---|
| 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
|