CVE-2026-79706

Breeze Cache < 2.5.13 - Unauthenticated File Creation via Path Traversal

2026-08-28 00:00

Strategic Overview

Status: Patched in 2.5.13
Affected Plugin: Breeze Cache
Affected Version: < 2.5.13
CVSS: 5.3Medium
Weakness type: CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE: CVE-2026-79706

At a glance

CVE-2026-79706 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Breeze Cache WordPress plugin, affecting versions < 2.5.13. 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.5.13; sites on affected versions should update now. Disclosed August 2026, reported by Jakub Herman.

Vulnerability Overview

The Breeze Cache plugin for WordPress is vulnerable to Path Traversal in all versions up to 2.5.13. This is due to insufficient validation of a user supplied path. This makes it possible for unauthenticated attackers to create files outside of the intended directory.

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-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Breeze Cache < 2.5.13 takes no account at all. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Breeze Cache the fix is 2.5.13: builds < 2.5.13 are affected, anything from 2.5.13 onward is not.

Remediation

Update to version 2.5.13, 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. None of that substitutes for the fix: Breeze Cache 2.5.13 closes this, and updating the plugin is the step that ends it.

Firewall
Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-79706 https://www.wordfence.com/threat-intel/vulnerabilities/id/6d9734bd-54de-44ab-b369-7a9d9a9e0e29 https://nvd.nist.gov/vuln/detail/CVE-2026-79706

Related records

Other vulnerabilities in Breeze Cache

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/