WordPress plugin · Updated daily · Source: Wordfence Intelligence

Breeze Cache vulnerabilities: affected versions and fixes

Breeze Cache has 300,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Breeze Cache at a glance

  • 14 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Sep 16, 2026.
  • Ranked #164 by popularity on WordPress.org (300,000+ active installs).
  • The latest version is 2.6.5 (released Nov 17, 2026). The most recent security fix shipped in 2.5.15.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Breeze Cache version

Enter the Breeze Cache version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Breeze Cache”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Breeze Cache”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.6.5). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Breeze Cache vulnerabilities

  • Breeze Cache <= 2.5.14 - Unauthenticated Cache Poisoning

    Other weakness · CVE-2026-79713

    Affected versions: ≤ 2.5.14

    Fixed in: 2.5.15

    Severity: Medium 5.3 · Disclosed Sep 16, 2026

  • Breeze Cache < 2.5.13 - Unauthenticated File Creation via Path Traversal

    Arbitrary file read or deletion · CVE-2026-79706

    Affected versions: < 2.5.13

    Fixed in: 2.5.13

    Severity: Medium 5.3 · Disclosed Aug 28, 2026

  • Breeze Cache <= 2.5.12 - Missing Authorization to Unauthenticated Arbitrary Content Deletion

    Missing authorization · CVE-2026-73356

    Affected versions: ≤ 2.5.12

    Fixed in: 2.5.13

    Severity: Medium 5.3 · Disclosed Aug 14, 2026

  • Breeze Cache <= 2.5.5 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-10551

    Affected versions: ≤ 2.5.5

    Fixed in: 2.5.6

    Severity: High 7.2 · Disclosed Jun 22, 2026

  • Breeze Cache <= 2.5.2 - Unauthenticated Exposure of Sensitive Information to an Unauthorized Actor via Crafted Login Cookie

    Other weakness · CVE-2026-2128

    Affected versions: ≤ 2.5.2

    Fixed in: 2.5.3

    Severity: Medium 5.3 · Disclosed May 28, 2026

  • Breeze Cache <= 2.4.4 - Unauthenticated Arbitrary File Upload via fetch_gravatar_from_remote

    Arbitrary file upload · CVE-2026-3844

    Affected versions: ≤ 2.4.4

    Fixed in: 2.4.5

    Severity: Critical 9.8 · Disclosed Apr 22, 2026

  • Breeze – WordPress Cache Plugin <= 2.2.21 - Missing Authorization to Cache Deletion

    Missing authorization · CVE-2025-13864

    Affected versions: ≤ 2.2.21

    Fixed in: 2.2.22

    Severity: Medium 5.3 · Disclosed Feb 18, 2026

  • Breeze <= 2.2.21 - Missing Authorization

    Missing authorization · CVE-2025-69364

    Affected versions: ≤ 2.2.21

    Fixed in: 2.2.22

    Severity: Medium 5.3 · Disclosed Jan 13, 2026

  • Breeze <= 2.2.13 - Missing Authorization

    Missing authorization · CVE-2025-23999

    Affected versions: ≤ 2.2.13

    Fixed in: 2.2.14

    Severity: Medium 4.3 · Disclosed Jun 18, 2025

  • Breeze <= 2.1.14 - Missing Authorization

    Missing authorization · CVE-2024-50422

    Affected versions: ≤ 2.1.14

    Fixed in: 2.1.15

    Severity: Medium 5.3 · Disclosed Oct 24, 2024

  • Breeze <= 2.1.14 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-50431

    Affected versions: ≤ 2.1.14

    Fixed in: 2.1.15

    Severity: Medium 4.4 · Disclosed Oct 24, 2024

  • Breeze <= 2.1.3 - Authenticated (Administrator+) Stored Cross-Site Scripting via breeze_api_token

    Cross-site scripting (XSS) · CVE-2024-27188

    Affected versions: ≤ 2.1.3

    Fixed in: 2.1.4

    Severity: Medium 5.5 · Disclosed Mar 25, 2024

  • Breeze <= 2.0.8 - Cross-Site Request Forgery via import_json_settings

    Cross-site request forgery (CSRF)

    Affected versions: ≤ 2.0.8

    Fixed in: 2.0.9

    Severity: Medium 4.3 · Disclosed Sep 19, 2022

  • Breeze – WordPress Cache Plugin <= 2.0.2 - Unprotected AJAX Actions

    Missing authorization · CVE-2022-29444

    Affected versions: ≤ 2.0.2

    Fixed in: 2.0.3

    Severity: Medium 6.5 · Disclosed May 2, 2022

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 16, 2026.

Most common weaknesses in Breeze Cache

Missing authorization

6 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Cross-site scripting (XSS)

3 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Arbitrary file read or deletion

1 issue

An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.

Frequently asked questions

Is Breeze Cache safe to use?

Breeze Cache is a well-known plugin with 300,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.6.5) and turn on automatic updates.

How do I find which version of Breeze Cache my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesBreeze Cache on WordPress.org