CVE-2026-79713 Breeze Cache 1.2.5 - 2.5.14 - Unauthenticated Cache Poisoning via Unkeyed Tracking Parameters

Medium 6.5 Published Updated

Unauthenticated attackers can poison the page cache by omitting tracking parameters from the cache key, serving malicious content to all visitors.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-79713?

CVE-2026-79713 is a medium-severity vulnerability in Unknown Breeze Cache, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-444

Which versions are affected by CVE-2026-79713?

How do I fix CVE-2026-79713?

No fix has been published for CVE-2026-79713 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-79713 being exploited?

There is no known exploitation of CVE-2026-79713 in the wild and no public exploit code.

Sources

Also known as GHSA-7m74-3h9w-8cpx.

Is CVE-2026-79713 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free