CVE-2026-2128: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in cloudways Breeze Cache
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.
AI Analysis
Technical Summary
The Breeze WordPress plugin improperly handles the wordpress_logged_in_ cookie in the inc/cache/execute-cache.php file when caching logged-in users. It extracts the username from the cookie without verifying the cryptographic signature or session validity against WordPress core. This flaw allows unauthenticated attackers to supply a crafted cookie (e.g., wordpress_logged_in_fake=admin|fake) to access cached HTML content generated for administrators, leading to exposure of sensitive information such as private posts, admin interface elements, and security tokens.
Potential Impact
An unauthenticated attacker can gain access to cached content intended for authenticated users, including administrators. This results in the disclosure of sensitive information such as private posts (full content), the WordPress Admin Bar, nonces, and other data normally restricted to logged-in users. The vulnerability does not affect integrity or availability but compromises confidentiality.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to disable the "Cache Logged-in Users" setting in the Breeze plugin to prevent exposure of sensitive cached content to unauthorized actors.
CVE-2026-2128: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in cloudways Breeze Cache
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.
CVSS v3.1
Score 5.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Breeze WordPress plugin improperly handles the wordpress_logged_in_ cookie in the inc/cache/execute-cache.php file when caching logged-in users. It extracts the username from the cookie without verifying the cryptographic signature or session validity against WordPress core. This flaw allows unauthenticated attackers to supply a crafted cookie (e.g., wordpress_logged_in_fake=admin|fake) to access cached HTML content generated for administrators, leading to exposure of sensitive information such as private posts, admin interface elements, and security tokens.
Potential Impact
An unauthenticated attacker can gain access to cached content intended for authenticated users, including administrators. This results in the disclosure of sensitive information such as private posts (full content), the WordPress Admin Bar, nonces, and other data normally restricted to logged-in users. The vulnerability does not affect integrity or availability but compromises confidentiality.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to disable the "Cache Logged-in Users" setting in the Breeze plugin to prevent exposure of sensitive cached content to unauthorized actors.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-06T19:47:59.101Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a191e25e29bf47b508f137c
Added to database: 5/29/2026, 5:03:33 AM
Last enriched: 5/29/2026, 5:18:26 AM
Last updated: 5/29/2026, 8:38:26 PM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.