Breeze – WordPress Cache Plugin <= 2.0.2 - Unprotected AJAX Actions
Strategic Overview
- Status
- Patched in 2.0.3
- Affected Plugin
- Breeze Cache
- Affected Version
<= 2.0.2- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-29444
At a glance
CVE-2022-29444 is a medium-severity Missing Authorization vulnerability in the Breeze Cache WordPress plugin, affecting versions <= 2.0.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). The issue is fixed in version 2.0.3; sites on affected versions should update now. Disclosed May 2022, reported by Dave Jong.
Vulnerability Overview
Plugin Settings Change leading to Cross-Site Scripting (XSS) vulnerability in Cloudways Breeze plugin <= 2.0.2 on WordPress allows users with a subscriber or higher user role to execute any of the wp_ajax_* actions in the class Breeze_Configuration which includes the ability to change any of the plugin's settings including CDN setting which could be further used for XSS attack.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-862: Missing Authorization
Reaching this weakness in Breeze Cache <= 2.0.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Breeze Cache the fix is 2.0.3: builds <= 2.0.2 are affected, anything from 2.0.3 onward is not.
Remediation
Update to version 2.0.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Breeze Cache 2.0.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.3CVE-2026-73356: Breeze Cache Unauthenticated Arbitrary Content
CVE-2026-73356 - 5.3CVE-2025-13864: Breeze – WordPress Cache Plugin Cache Deletion
CVE-2025-13864 - 5.3CVE-2025-69364: Breeze <= 2.2.21 Missing Authorization
CVE-2025-69364 - 5.3CVE-2024-50422: Breeze <= 2.1.14 Missing Authorization
CVE-2024-50422
Other vulnerabilities in Breeze Cache
- 9.8CVE-2026-3844: Breeze Cache <= 2.4.4 Arbitrary File Upload
CVE-2026-3844 - 7.2CVE-2026-10551: Breeze Cache <= 2.5.5 Stored Cross-Site Scripting
CVE-2026-10551 - 5.5CVE-2024-27188: Breeze <= 2.1.3 Stored Cross-Site Scripting
CVE-2024-27188 - 5.3CVE-2026-79706: Breeze Cache < 2.5.13 File Creation
CVE-2026-79706 - 5.3CVE-2026-2128: Breeze Cache Exposure of Sensitive Information
CVE-2026-2128 - 4.4CVE-2024-50431: Breeze <= 2.1.14 Stored Cross-Site Scripting
CVE-2024-50431 - 4.3CVE-2025-23999: Breeze <= 2.2.13 Missing Authorization
CVE-2025-23999 - 4.3Breeze <= 2.0.8 Cross-Site Request Forgery via import_json_settings
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C