External risk intelligence

WordPress Breeze plugin lets attackers upload files to take over your site if Gravatar feature is on.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-3844

An external attacker could exploit a flaw in the Breeze Cache for WordPress plugin to upload malicious files, provided the "Host Files Locally" feature is enabled. This could lead to a full takeover of the web server, risking sensitive customer data and site availability.

3Halo Surface Signal

Unrestricted File Upload

External exposure likelihood

Halo Surface Signal score for CVE-2026-3844

The vulnerability affects a public-facing WordPress plugin, which is typically internet-accessible. However, the exploit requires the specific 'Host Files Locally - Gravatars' feature to be enabled, which is not the default configuration. Because it relies on a non-default setting, the reachability of the vulnerable surface is possible rather than likely.

Horizon Alert

Summary of the vulnerability and why it matters

The Breeze Cache plugin for WordPress has a vulnerability that allows unauthenticated attackers to upload arbitrary files. This could potentially lead to remote code execution on your site's server. The issue lies in how the plugin handles certain file uploads, specifically when fetching Gravatars.

  • Attackers can upload malicious files.
  • Requires a specific plugin setting to be enabled.
  • Affects WordPress sites using the plugin.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this flaw by uploading arbitrary files to a WordPress site if the "Host Files Locally - Gravatars" setting is enabled. This could allow the attacker to achieve remote code execution by uploading a malicious script or executable.

  • Unauthenticated attacker
  • Target: WordPress site
  • Precondition: Gravatar local hosting enabled

Live Threat

Current exploitation, exposure, and threat context

This vulnerability allows unauthenticated attackers to upload arbitrary files to an affected WordPress server, potentially enabling remote code execution. Attackers often favor such vulnerabilities due to the direct path they offer to compromise a system. However, exploitation requires a specific, non-default setting to be enabled.

  • Exploitation requires a disabled-by-default setting.
  • No publicly reported exploitation is evident.
  • The vulnerability was recently disclosed.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize patching the Breeze Cache plugin to version 2.4.4 or later to address the arbitrary file upload vulnerability. If immediate patching is not feasible, disable the "Host Files Locally - Gravatars" setting to mitigate the risk.

  • Update Breeze Cache plugin.
  • Disable "Host Files Locally - Gravatars".
  • Monitor for unauthorized file uploads.

Frequently asked questions

What is the Breeze Cache plugin for WordPress?

The Breeze Cache plugin is a tool used for WordPress websites that helps improve website performance by caching content. It's designed to make websites load faster for visitors.

What is CVE-2026-3844 and what kind of weakness does it represent?

CVE-2026-3844 is a critical vulnerability in the Breeze Cache WordPress plugin. It's classified as an arbitrary file upload weakness (CWE-434), meaning an attacker can upload any type of file to the server.

How can an attacker exploit this vulnerability?

An attacker can exploit this by uploading malicious files if the "Host Files Locally - Gravatars" setting within the Breeze Cache plugin is enabled. This specific setting is disabled by default, acting as a precondition for exploitation.

Why should I care about this threat if my servers are internal?

While this vulnerability affects a plugin typically used on internet-facing websites, it's important to note that the Halo Surface Signal indicates a 'Possible' exposure. This means that if the affected plugin and its specific Gravatar setting are enabled on any internal server that is accessible, even from within your network, it could still pose a risk.

What is the first step to protect my WordPress site from this threat?

The most important first step is to update your Breeze Cache plugin to version 2.4.4 or later. If updating immediately isn't possible, you should disable the "Host Files Locally - Gravatars" setting to mitigate the risk.

References