Live › vulnerability › CVE-2026-120551
WP Compress, a WordPress performance plugin, fails to check authorization on some actions, so an unauthenticated attacker can link the site to their own WP Compress account and overwrite its settings. The attacker can also obtain the shared API key, which lets them purge caches, delete files and invalidate the opcode cache on the site.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 05:48 UTC. All times on this page are UTC.
Sites running the WP Compress plugin version 7.22.01 or earlier where no API key is stored, which covers fresh installations and lite or free-mode installs. The flaw lets an unauthenticated visitor reach endpoints that the plugin guards only when a stored key exists. Sites with the plugin absent, or with a stored API key and a newer version, are not described as exposed.
No product ranges from the sources yet.
7.22.01 or earlier in the WordPress plugins screen.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The WP Compress – Instant Performance & Speed Optimization plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.22.01. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to link the victim site to an attacker-controlled WP Compress account, overwrite plugin settings to an aggressive live-CDN preset, and gain the shared api_key that authenticates all nopriv HMAC-gated endpoints — enabling full control over cache purging, file deletion, opcode cache invalidation, and other privileged plugin operations. This vulnerability only affects fresh installations or lite/free-mode installs where no api_key is already stored, as the sole guard fails open when the stored key is absent.
This page as .md · .json · in your agent: get_signal("CVE-2026-120551")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.