WordPress security changelog
MEDIUM CVE-2026-79713 Deferred

Breeze Cache: Tracking parameters poison the clean page-cache entry

The Breeze Cache WordPress plugin before 2.5.15 does not include a set of tracking-related query parameters in its page-cache key while still caching pages requested with them, allowing unauthenticated attackers to have a page rendered under their own request context stored under, and served from, the clean URL's cache entry to every subsequent visitor. The effect depends on how those parameters influence rendering; a specific stolen-data or script-execution outcome is not established by the export. Affected versions reported by the CNA: 1.2.5 to < 2.5.15. The export identifies 2.5.15 as fixed.

CVE / CNA score 6.5 CVSS 3.1 · contact@wpscan.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Breeze Cache
Plugin slug
breeze
Affected
1.2.5 to < 2.5.15
Safe version
2.5.15
Published
Sep 18, 2026
Weakness
CWE-444

This CVE was published Sep 18, 2026 and is one of 11 known issues for this plugin.

Update, patch or deactivate.

The authoritative export identifies 2.5.15 as fixed. Update to that release or a later supported version. Do not cache requests whose ignored parameters can affect output, or include normalized relevant inputs in the cache key. Clear existing page caches after updating.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

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 WordPress plugin before 2.5.15 does not include a set of tracking-related query parameters in its page-cache key while still caching pages requested with them, allowing unauthenticated attackers to have a page rendered under their own request context stored under, and served from, the clean URL's cache entry to every subsequent visitor.

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

Primary and upstream sources