Breeze Cache: known security problems
14 known security problems reported for this WordPress plugin, with the affected versions, the fix and what to do.
Updated
In short
There are 14 known security problems on this page. Each one has a fixed version. Updating to version 2.5.15 or newer covers every fixed problem listed here.
Based on public reports. Check the plugin’s changelog. Watchfox AI may be wrong.
Get an email when your site is affected: install Watchfox AI (free)
A stranger could use it to harm your site (up to and including 2.5.14)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.5.14
- Fixed in
- 2.5.15
- What to do
- If your site has an affected version, update Breeze Cache to version 2.5.15 or newer.
- Official ID
- CVE-2026-79713
- Report title
- Breeze Cache <= 2.5.14 - Unauthenticated Cache Poisoning
- First reported
- Sources
- Wordfence, seen
A stranger could read or delete private files on your server
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Before 2.5.13
- Fixed in
- 2.5.13
- What to do
- If your site has an affected version, update Breeze Cache to version 2.5.13 or newer.
- Official ID
- CVE-2026-79706
- Report title
- Breeze Cache < 2.5.13 - Unauthenticated File Creation via Path Traversal
- First reported
- Sources
- Wordfence, seen
A stranger could do things on your site they should not be allowed to
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.5.12
- Fixed in
- 2.5.13
- What to do
- If your site has an affected version, update Breeze Cache to version 2.5.13 or newer.
- Official ID
- CVE-2026-73356
- Report title
- Breeze Cache <= 2.5.12 - Missing Authorization to Unauthenticated Arbitrary Content Deletion
- First reported
- Sources
- Wordfence, seen
A stranger could plant harmful code that runs for your visitors or admins
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.5.5
- Fixed in
- 2.5.6
- What to do
- If your site has an affected version, update Breeze Cache to version 2.5.6 or newer.
- Official ID
- CVE-2026-10551
- Report title
- Breeze Cache <= 2.5.5 - Unauthenticated Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
A stranger could use it to harm your site (up to and including 2.5.2)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.5.2
- Fixed in
- 2.5.3
- What to do
- If your site has an affected version, update Breeze Cache to version 2.5.3 or newer.
- Official ID
- CVE-2026-2128
- Report title
- Breeze Cache <= 2.5.2 - Unauthenticated Exposure of Sensitive Information to an Unauthorized Actor via Crafted Login Cookie
- First reported
- Sources
- Wordfence, seen
A stranger could run their own code on your site and take it over
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.4.4
- Fixed in
- 2.4.5
- What to do
- If your site has an affected version, update Breeze Cache to version 2.4.5 or newer.
- Official ID
- CVE-2026-3844
- Report title
- Breeze Cache <= 2.4.4 - Unauthenticated Arbitrary File Upload via fetch_gravatar_from_remote
- First reported
- Sources
- Wordfence, seen
Someone could do things on your site they should not be allowed to (up to and including 2.2.21)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.2.21
- Fixed in
- 2.2.22
- What to do
- If your site has an affected version, update Breeze Cache to version 2.2.22 or newer.
- Official ID
- CVE-2025-13864
- Report title
- Breeze – WordPress Cache Plugin <= 2.2.21 - Missing Authorization to Cache Deletion
- First reported
- Sources
- Wordfence, seen
Someone could do things on your site they should not be allowed to (up to and including 2.2.21) (2)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.2.21
- Fixed in
- 2.2.22
- What to do
- If your site has an affected version, update Breeze Cache to version 2.2.22 or newer.
- Official ID
- CVE-2025-69364
- Report title
- Breeze <= 2.2.21 - Missing Authorization
- First reported
- Sources
- Wordfence, seen
Someone could do things on your site they should not be allowed to (up to and including 2.2.13)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.2.13
- Fixed in
- 2.2.14
- What to do
- If your site has an affected version, update Breeze Cache to version 2.2.14 or newer.
- Official ID
- CVE-2025-23999
- Report title
- Breeze <= 2.2.13 - Missing Authorization
- First reported
- Sources
- Wordfence, seen
Someone who already has an admin account could plant harmful code that runs for your visitors or admins (up to and including 2.1.14)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.1.14
- Fixed in
- 2.1.15
- What to do
- If your site has an affected version, update Breeze Cache to version 2.1.15 or newer.
- Official ID
- CVE-2024-50431
- Report title
- Breeze <= 2.1.14 - Authenticated (Administrator+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone could do things on your site they should not be allowed to (up to and including 2.1.14)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.1.14
- Fixed in
- 2.1.15
- What to do
- If your site has an affected version, update Breeze Cache to version 2.1.15 or newer.
- Official ID
- CVE-2024-50422
- Report title
- Breeze <= 2.1.14 - Missing Authorization
- First reported
- Sources
- Wordfence, seen
Someone who already has an admin account could plant harmful code that runs for your visitors or admins (up to and including 2.1.3)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.1.3
- Fixed in
- 2.1.4
- What to do
- If your site has an affected version, update Breeze Cache to version 2.1.4 or newer.
- Official ID
- CVE-2024-27188
- Report title
- Breeze <= 2.1.3 - Authenticated (Administrator+) Stored Cross-Site Scripting via breeze_api_token
- First reported
- Sources
- Wordfence, seen
Someone could trick a logged-in admin into changing settings without knowing
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.8
- Fixed in
- 2.0.9
- What to do
- If your site has an affected version, update Breeze Cache to version 2.0.9 or newer.
- Report title
- Breeze <= 2.0.8 - Cross-Site Request Forgery via import_json_settings
- First reported
- Sources
- Wordfence, seen
Someone could use it to harm your site
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.2
- Fixed in
- 2.0.3
- What to do
- If your site has an affected version, update Breeze Cache to version 2.0.3 or newer.
- Official ID
- CVE-2022-29444
- Report title
- Breeze – WordPress Cache Plugin <= 2.0.2 - Unprotected AJAX Actions
- First reported
- Sources
- Wordfence, seen
Where this comes from
We collect these reports from public security sources and rewrite them in plain words. Each problem shows its sources and the date we first saw it. This page never says whether your own site is affected: only a check of your site’s versions can tell.
Get an email when your site is affected.
Install Watchfox AI once. It checks your plugins and themes against this list every day, for free.
Install Watchfox AI (free)