Asset CleanUp: Page Speed Booster
wp-asset-clean-up · plugin
Known security vulnerabilities for Asset CleanUp: Page Speed Booster. Find out in seconds which version runs on your site with WP Lens.
7 known vulnerabilities
3 exploitable without logging in · latest Sep 25, 2026
Listed on wordpress.org · latest 1.4.0.6 · last updated Sep 16, 2026 · 100K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2024-43314login required≤ 1.3.9.3
WordPress Asset CleanUp: Page Speed Booster plugin <= 1.3.9.3 - Broken Access Control vulnerability
- High 7.2
CVE-2026-13354unauthenticated≤ 1.4.0.5
Asset CleanUp: Page Speed Booster <= 1.4.0.5 - Unauthenticated Stored Cross-Site Scripting via Comment Content
- High 7.1
CVE-2026-66571unauthenticated · needs a click≤ 1.4.0.5
WordPress Asset CleanUp: Page Speed Booster plugin <= 1.4.0.5 - Cross Site Request Forgery (CSRF) vulnerability
- Medium 5.5
CVE-2026-12037admin≤ 1.4.0.5
Asset CleanUp: Page Speed Booster <= 1.4.0.5 - Authenticated (Administrator+) Server-Side Request Forgery via 'page_url' Parameter
- Medium 5.3
CVE-2026-45212unauthenticated≤ 1.4.0.3
WordPress Asset CleanUp: Page Speed Booster plugin <= 1.4.0.3 - Broken Access Control vulnerability
- Medium 4.8
CVE-2021-36899admin≤ 1.3.8.4
WordPress Asset CleanUp: Page Speed Booster plugin <= 1.3.8.4 - Authenticated Reflected Cross-Site Scripting (XSS) vulnerability
- Medium 4.4
CVE-2024-53738high privilege≤ 1.3.9.8
WordPress Asset CleanUp: Page Speed Booster plugin <=1.3.9.8 - Server Side Request Forgery (SSRF) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).