CVE-2026-100181: Asset CleanUp: Page Speed Booster (WordPress plugin) · Cross-site Scripting
Affects Asset CleanUp: Page Speed Booster (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 18 Nov 2026, 12:04 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 5.4 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| gabelivanAsset CleanUp: Page Speed Booster | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisories for updates. Until a fix is available, consider disabling or removing the plugin if feasible, or restricting access to affected pages to trusted users only. Avoid relying solely on wp_kses sanitization due to the plugin's flawed post-processing. Implementing additional web application firewall (WAF) rules to detect and block malicious payloads in the 'comment' parameter may provide temporary mitigation.
Description
The Asset CleanUp: Page Speed Booster WordPress plugin up to version 1.4.0.6 is vulnerable to stored cross-site scripting (XSS) via the 'comment' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts that execute when users view the affected pages. The issue persists despite wp_kses sanitization because the plugin's own regex-based replacements corrupt the HTML structure, enabling the XSS payload.
References
- wordfence.com/threat-intel/vulnerabilities/id/06bc0988-5a70-4e1e-b66d-ca161138cfc2?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeJs.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeJs.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeCommon.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeCommon.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3802308%40wp-asset-clean-up&new=3802308%40wp-asset-clean-up (opens in a new tab)