dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13864

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Breeze - WordPress Cache Plugin plugin for WordPress is vulnerable to unauthorized cache clearing in all versions up to, and including, 2.2.21. This is due to the REST API endpoint `/wp-json/breeze/v1/clear-all-cache` being registered with `permission_callback => '__return_true'` and authentication being disabled by default when the API is enabled. This makes it possible for unauthenticated attackers to clear all site caches (page cache, Varnish, and Cloudflare) via a simple POST request, granted the administrator has enabled the API integration feature.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Breeze WordPress cache plugin registers a REST API endpoint at /wp-json/breeze/v1/clear-all-cache with permission_callback set to '__return_true', which allows any request to pass without authorization checks. Combined with authentication being disabled by default when the API is enabled, unauthenticated attackers can clear all site caches (page, Varnish, Cloudflare) via a simple POST request.

MitigationUpdate the REST API endpoint's permission_callback to enforce proper authentication (e.g., check for user capabilities or require a valid nonce), or disable the API integration feature if not required. Consider applying any vendor security patches for versions up to 2.2.21.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Breeze plugin is installed
    Check the installed plugins in WordPress at wp-admin/plugins.php or via WP-CLI: wp plugin list --name=breeze
    Affected if Breeze plugin version 2.2.21 or earlier is installed
  2. Confirm the REST API endpoint is enabled
    Make a GET request to /wp-json/breeze/v1/clear-all-cache or check the Breeze settings at wp-admin/admin.php?page=breeze#api-integration
    Affected if The endpoint responds or the API integration setting is enabled in the plugin configuration
  3. Inspect the endpoint permission_callback
    Examine the plugin source code in wp-content/plugins/breeze/includes/api/clear-all-cache.php (or similar path) for the REST route registration and verify permission_callback is set to '__return_true' or lacks capability checks
    Affected if permission_callback returns true for all requests without verifying user capabilities or authentication
  4. Check if API authentication is disabled
    In WordPress admin, go to Breeze settings > API Integration (or equivalent) and verify the setting that controls REST API authentication is disabled or not properly enforced
    Affected if Authentication for the Breeze REST API is disabled or not configured, allowing unauthenticated access
  5. Test endpoint accessibility (optional)
    Send a POST request to /wp-json/breeze/v1/clear-all-cache without providing any authentication credentials
    Affected if The request succeeds without returning an authorization error (401/403) and triggers cache clearing

A user is affected if the Breeze plugin versions 2.2.21 or earlier are installed with the REST API endpoint enabled and permission_callback allowing unauthenticated access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the REST API endpoint's permission_callback to enforce proper authentication (e.g., check for user capabilities or require a valid nonce), or disable the API integration feature if not required. Consider applying any vendor security patches for versions up to 2.2.21.

Recommended fix Moderate confidence

Breeze version 2.2.22 or later

  1. Update the Breeze plugin to version 2.2.22 or later via the WordPress admin dashboard (Plugins > All Plugins > Breeze > Update Now), or via WP-CLI: wp plugin update breeze

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13864 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data