CVE-2026-3844

Breeze Cache <= 2.4.4 - Unauthenticated Arbitrary File Upload via fetch_gravatar_from_remote

2026-04-22 13:59
bashu

Strategic Overview

Status
Patched in 2.4.5
Affected Plugin
Breeze Cache
Affected Version
<= 2.4.4
CVSS
9.8Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2026-3844
View all Breeze Cache vulnerabilities

At a glance

CVE-2026-3844 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Breeze Cache WordPress plugin, affecting versions <= 2.4.4. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.4.5; sites on affected versions should update now. Disclosed April 2026, reported by bashu.

Vulnerability Overview

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.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Breeze Cache <= 2.4.4 carries this weakness at fetch_gravatar_from_remote, and reaching it takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Breeze Cache the fix is 2.4.5: builds <= 2.4.4 are affected, anything from 2.4.5 onward is not.

Remediation

Update to version 2.4.5, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Breeze Cache 2.4.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-3844https://www.wordfence.com/threat-intel/vulnerabilities/id/e342b1c0-6e7f-4e2c-8a52-018df12c12a0https://nvd.nist.gov/vuln/detail/CVE-2026-3844

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C