Skip to main content
VulnerabilityPublished

CVE-2026-104013: WP Compress – Instant Performance & Speed Optimization · Path Traversal

Affects WP Compress – Instant Performance & Speed OptimizationSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 21 Nov 2026, 09:45 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
aresitWP Compress – Instant Performance & Speed OptimizationAffected
  • <=7.26.00
Fixed in–

AI-suggested

Users should verify if the plugin's cookie-cache feature is enabled and consider disabling it or removing tracked cookies to mitigate risk. Monitor the vendor's advisory channels for updates and apply any official fixes once available. Until then, restrict access to sensitive files and consider additional web application firewall rules to block suspicious path traversal attempts targeting the 'css' parameter.

Description

The WP Compress – Instant Performance & Speed Optimization WordPress plugin is vulnerable to a directory traversal flaw in all versions up to and including 7.26.00. This vulnerability allows unauthenticated attackers to read arbitrary files on the server by exploiting the 'css' parameter. Successful exploitation requires the plugin's cookie-cache feature to be enabled with at least one tracked cookie name configured, as the attack involves injecting a path traversal sequence into a cookie such as pll_language.

References

Community reviews

Loading reviews…