Strategic Overview
- Status
- Patched in 2.1.15
- Affected Plugin
- Breeze Cache
- Affected Version
<= 2.1.14- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-50422
At a glance
CVE-2024-50422 is a medium-severity Missing Authorization vulnerability in the Breeze Cache WordPress plugin, affecting versions <= 2.1.14. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.15; sites on affected versions should update now. Disclosed October 2024, reported by Rafie Muhammad.
Vulnerability Overview
The Breeze plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the reset_to_default() function in versions up to, and including, 2.1.14. This makes it possible for unauthenticated attackers to reset to default settings.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Breeze Cache <= 2.1.14 carries this weakness at reset_to_default(), and reaching it 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.1.15: builds <= 2.1.14 are affected, anything from 2.1.15 onward is not.
Remediation
Update to version 2.1.15, 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.1.15 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 6.5CVE-2022-29444: Breeze – WordPress Cache Unprotected AJAX Actions
CVE-2022-29444 - 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
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