CVE-2026-100181Asset CleanUp: Page Speed Booster <= 1.4.0.6 - Unauthenticated Stored Cross-Site Scripting via Comment Content
- 5.4MediumCVSS base score
- 0.35%Exploitation in 30 daysEPSS · top 70% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
The Asset CleanUp: Page Speed Booster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.4.0.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit succeeds even though wp_kses is applied on save, because the XSS is manufactured post-sanitization by the plugin's regex pass: kses-permitted tags such as <a title> and <code> carry the attacker's marker and terminator strings intact into the rendered HTML buffer, where the plugin's own replacement then corrupts the document structure.
Timeline
ID reserved
By Wordfence
- 54 days later
· 54 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| WordfenceCNA (assigner) | 3.1 | Medium5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
| NVDNVD · Deferred | 3.1 | Medium5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
- EPSS (exploitation in 30 days)
- 0.35% · top 70% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.4.
Affected products
gabelivan · Asset CleanUp: Page Speed Booster
- affected ≤ 1.4.0.6
References
References6
- https://www.wordfence.com/threat-intel/vulnerabilities/id/06bc0988-5a70-4e1e-b66d-ca161138cfc2?source=cve (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeJs.php#L1064 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeJs.php#L1063 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeCommon.php#L666 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeCommon.php#L767 (opens in a new tab)
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3802308%40wp-asset-clean-up&new=3802308%40wp-asset-clean-up (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-128546 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-100181)Record last updated .