Skip to content
Noroxi

Breeze Cache

breeze · plugin

Known security vulnerabilities for Breeze Cache. Find out in seconds which version runs on your site with WP Lens.

10 known vulnerabilities

1 critical · 6 exploitable without logging in · 1 with public exploit code · latest Aug 18, 2026

Listed on wordpress.org · latest 2.6.0 · last updated Sep 29, 2026 · 300K+ installs

wordpress.org status checked on Oct 2, 2026

Vulnerabilities

  • CVE-2026-3844unauthenticated≤ 2.4.4

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

    Critical 9.8
  • CVE-2026-73356unauthenticated≤ 2.5.12

    WordPress Breeze plugin <= 2.5.12 - Arbitrary Content Deletion vulnerability

    High 8.2
  • CVE-2024-50431high privilege≤ 2.1.14

    WordPress Breeze plugin <= 2.1.14 - Cross Site Scripting (XSS) vulnerability

    Medium 5.9
  • CVE-2024-27188high privilege≤ 2.1.3

    WordPress Breeze plugin <= 2.1.3 - Cross Site Scripting (XSS) vulnerability

    Medium 5.9
  • CVE-2022-29444subscriber+≤ 2.0.2

    WordPress Breeze plugin <= 2.0.2 - Plugin Settings Change leading to Cross-Site Scripting (XSS) vulnerability

    Medium 5.4
  • CVE-2026-2128unauthenticated≤ 2.5.2

    Breeze Cache <= 2.5.2 - Unauthenticated Exposure of Sensitive Information to an Unauthorized Actor via Crafted Login Cookie

    Medium 5.3
  • CVE-2025-13864unauthenticated≤ 2.2.21

    Breeze – WordPress Cache Plugin <= 2.2.21 - Missing Authorization to Cache Deletion

    Medium 5.3
  • CVE-2025-69364unauthenticated≤ 2.2.21

    WordPress Breeze plugin <= 2.2.21 - Broken Access Control vulnerability

    Medium 5.3
  • CVE-2024-50422unauthenticated≤ 2.1.14

    WordPress Breeze plugin <= 2.1.14 - Broken Access Control vulnerability

    Medium 5.3
  • CVE-2025-23999login required≤ 2.2.13

    WordPress Breeze plugin <= 2.2.13 - Broken Access Control vulnerability

    Medium 4.3

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory