CVE-2026-66571

Asset CleanUp: Page Speed Booster <= 1.4.0.5 - Cross-Site Request Forgery

2026-09-17 12:06
Helder Gonçalves

Strategic Overview

Status
Patched in 1.4.0.6
Affected Plugin
Asset CleanUp: Page Speed Booster
Affected Version
<= 1.4.0.5
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-66571
View all Asset CleanUp: Page Speed Booster vulnerabilities

At a glance

CVE-2026-66571 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Asset CleanUp WordPress plugin, affecting versions <= 1.4.0.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.4.0.6; sites on affected versions should update now. Disclosed September 2026, reported by Helder Gonçalves.

Vulnerability Overview

The Asset CleanUp: Page Speed Booster plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.0.5. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Asset CleanUp <= 1.4.0.5 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Asset CleanUp the fix is 1.4.0.6: builds <= 1.4.0.5 are affected, anything from 1.4.0.6 onward is not.

Remediation

Update to version 1.4.0.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Asset CleanUp: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Asset CleanUp 1.4.0.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-66571https://www.wordfence.com/threat-intel/vulnerabilities/id/d024347c-5347-452d-9229-2993ba34d767https://nvd.nist.gov/vuln/detail/CVE-2026-66571

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C