Breeze Cache: Dangerous file upload
Breeze Cache is affected by dangerous file upload. The vulnerable path is reachable without authentication. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise. The published affected range is <= 2.4.4.
- Component
- Breeze Cache
- Plugin slug
breeze- Affected
- <= 2.4.4
- Safe version
- See mitigation notes
- Published
- Apr 23, 2026
This CVE was published Apr 23, 2026 and is one of 11 known issues for this plugin.
Update, patch or deactivate.
No fixed release is identified. Update Breeze Cache when a release after 2.4.4 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 2.5.13, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Breeze Cache plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'fetch_gravatar_from_remote' function in all versions up to, and including, 2.4.4. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. The vulnerability can only be exploited if "Host Files Locally - Gravatars" is enabled, which is disabled by default.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H