Breeze <= 2.1.3 - Authenticated (Administrator+) Stored Cross-Site Scripting via breeze_api_token
Strategic Overview
- Status
- Patched in 2.1.4
- Affected Plugin
- Breeze Cache
- Affected Version
<= 2.1.3- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2024-27188
At a glance
CVE-2024-27188 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Breeze Cache WordPress plugin, affecting versions <= 2.1.3. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 2.1.4; sites on affected versions should update now. Disclosed March 2024, reported by Jorge Diaz (ddiax).
Vulnerability Overview
The Breeze plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘breeze_api_token’ parameter in versions up to, and including, 2.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only impacts multi-site installations and installations where unfiltered_html has been disabled.
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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Breeze Cache <= 2.1.3 carries this weakness at breeze_api_token, and reaching it takes an account at Administrator level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Breeze Cache the fix is 2.1.4: builds <= 2.1.3 are affected, anything from 2.1.4 onward is not.
Remediation
Update to version 2.1.4, or a newer patched version
How does WordSec protect against this?
An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Breeze Cache 2.1.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Breeze Cache
- 9.8CVE-2026-3844: Breeze Cache <= 2.4.4 Arbitrary File Upload
CVE-2026-3844 - 6.5CVE-2022-29444: Breeze – WordPress Cache Unprotected AJAX Actions
CVE-2022-29444 - 5.3CVE-2026-79706: Breeze Cache < 2.5.13 File Creation
CVE-2026-79706 - 5.3CVE-2026-73356: Breeze Cache Unauthenticated Arbitrary Content
CVE-2026-73356 - 5.3CVE-2026-2128: Breeze Cache Exposure of Sensitive Information
CVE-2026-2128 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C