CVE-2026-2128 Information disclosure in Breeze Cache
Unauthenticated attackers can expose sensitive administrator data by crafting a login cookie when the cache logged-in users setting is enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-2128?
CVE-2026-2128 is a medium-severity vulnerability in cloudways Breeze Cache, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Breeze plugin for WordPress is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in all versions up to, and including, 2.5.2 This is due to improper verification of the `wordpress_logged_in_` cookie in the `inc/cache/execute-cache.php` file when the "Cache Logged-in Users" setting is enabled. The plugin parses the username directly from the cookie value (e.g., `username|hash`) using `substr()` to retrieve the corresponding cache file but fails to verify the session's cryptographic signature or validity with WordPress core. This makes it possible for unauthenticated attackers to supply a crafted cookie (e.g., `wordpress_logged_in_fake=admin|fake`) to trick the plugin into serving the cached HTML content generated for an administrator, leading to the disclosure of sensitive information such as private posts (including their full content), the Admin Bar, WordPress nonces, and other data visible only to logged-in administrators or other users.
Weakness: CWE-200
Which versions are affected by CVE-2026-2128?
How do I fix CVE-2026-2128?
No fix has been published for CVE-2026-2128 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-2128 being exploited?
There is no known exploitation of CVE-2026-2128 in the wild and no public exploit code.
Sources
Also known as GHSA-mpqv-gg33-5mc7.