Breeze Cache
Approved changes feed: RSS · Atom
cpe:2.3:a:cloudways:breeze_cache:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Cloudways (14ea84fb-84ad-5353-b0d5-34b9d5953555) |
|---|---|
| Product | Breeze Cache (7edeea2a-5f90-51b9-8c04-162f35e5f8ac) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-3844 |
vulnerable | 2026-06-08 08:01:19.555312 |
Breeze Cache <= 2.4.4 - Unauthenticated Arbitrary File Upload via fetch_gravatar_from_remote
CRITICAL (9.8)
The Breeze Cache plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'fetch_gravatar_from_remote' function in all versions up to, and including, 2.4.4. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. The vulnerability can only be exploited if "Host Files Locally - Gravatars" is enabled, which is disabled by default.
Published: 2026-04-23T02:25:21.927Z
Updated: 2026-04-23T12:31:46.631Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2128 |
vulnerable | 2026-06-08 07:55:16.579312 |
Breeze Cache <= 2.5.2 - Unauthenticated Exposure of Sensitive Information to an Unauthorized Actor via Crafted Login Cookie
MEDIUM (5.3)
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.
Published: 2026-05-29T03:39:08.827Z
Updated: 2026-05-29T10:07:26.626Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-13864 |
vulnerable | 2026-06-08 07:06:32.845128 |
Breeze – WordPress Cache Plugin <= 2.2.21 - Missing Authorization to Cache Deletion
MEDIUM (5.3)
The Breeze - WordPress Cache Plugin plugin for WordPress is vulnerable to unauthorized cache clearing in all versions up to, and including, 2.2.21. This is due to the REST API endpoint `/wp-json/breeze/v1/clear-all-cache` being registered with `permission_callback => '__return_true'` and authentication being disabled by default when the API is enabled. This makes it possible for unauthenticated attackers to clear all site caches (page cache, Varnish, and Cloudflare) via a simple POST request, granted the administrator has enabled the API integration feature.
Published: 2026-02-19T04:36:12.578Z
Updated: 2026-04-08T16:54:59.642Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.