CVE
Asset CleanUp: Page Speed Booster unauthenticated stored XSS via comment content
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
Stored cross-site scripting in the Asset CleanUp: Page Speed Booster plugin for WordPress lets an unauthenticated attacker inject scripts through the comment content. Attackers can do this remotely, without logging in, and the injected scripts run in the browser of any user who opens an affected page.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.4/10CVSS 5.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-100181 (Asset CleanUp: Page Speed Booster <= 1.4.0.6 - Unauthenticated Stored Cross-Site Scripting via Comment Content), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-100181 (entry last updated 2026-11-18):
Affected:
- gabelivan Asset CleanUp: Page Speed Booster: through 1.4.0.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-100181 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-100181 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/06bc0988-5a70-4e1e-b66d-ca161138cfc2?source=cve
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeJs.php#L1064
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeJs.php#L1063
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeCommon.php#L666
- https://plugins.trac.wordpress.org/browser/wp-asset-clean-up/tags/1.4.0.6/classes/OptimiseAssets/OptimizeCommon.php#L767
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3802308%40wp-asset-clean-up&new=3802308%40wp-asset-clean-up
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-100181
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-100181"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- gabelivan Asset CleanUp: Page Speed Booster
through 1.4.0.6
Evidence 8
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-100181
Is CVE-2026-100181 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-100181?
Asset CleanUp: Page Speed Booster: through 1.4.0.6.Source: cve.now feed data