# 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.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-mpqv-gg33-5mc7

## 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 (Exposure of Sensitive Information to an Unauthorized Actor)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2128 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-2128 in the wild and no public exploit code.

Affected product: cloudways Breeze Cache. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2128/ (Markdown: https://insights.sbomify.com/CVE-2026-2128/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2128
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2128
- OSV: https://osv.dev/vulnerability/CVE-2026-2128

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2128/
Summaries are generated and may contain mistakes; the official description above is the record.