CVE-2026-17608

WP Compress <= 7.10.09 - Cross-Site Request Forgery to Arbitrary Options Deletion

2026-08-15 17:28
Wordfence PRISM

Strategic Overview

Status
Patched in 7.20.01
Affected Version
<= 7.10.09
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-17608
View all WP Compress – Instant Performance & Speed Optimization vulnerabilities

At a glance

CVE-2026-17608 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Compress WordPress plugin, affecting versions <= 7.10.09. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 7.20.01; sites on affected versions should update now. Disclosed August 2026, reported by Wordfence PRISM.

Vulnerability Overview

The WP Compress – Instant Performance & Speed Optimization plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 7.10.09. This is due to missing or incorrect nonce validation on the (top-level template code) function. This makes it possible for unauthenticated attackers to delete arbitrary WordPress options, including critical ones such as siteurl, home, active_plugins, template, and stylesheet, causing site outage or a full plugin and theme reset via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on integrity.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Compress <= 7.10.09 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Compress the fix is 7.20.01: builds <= 7.10.09 are affected, anything from 7.20.01 onward is not.

Remediation

Update to version 7.20.01, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Compress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Compress 7.20.01 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C