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

Published Sep 18, 2026
·
Updated

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.

Affected Software

1 affected component
WordPress Breeze Cache<2.5.15

Event History

Sep 18, 2026
CVE Published
via MITRE·06:11 AM
Data Sourced
via MITRE·06:11 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

WordPress sites using Breeze Cache versions 1.2.5 through 2.5.14 are affected. Version 2.5.15 is not described as affected.

2

Does exploitation require an account or user interaction?

No. The supplied vector identifies network-based exploitation with low attack complexity, no privileges required, and no user interaction required.

3

What is the practical impact of a successful attack?

An attacker can cause a page generated in their request context to be cached under the clean URL. Subsequent visitors may then receive that poisoned cached response, with low confidentiality and integrity impact indicated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203