CVE-2025-69364
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 · uneditedMissing Authorization vulnerability in Cloudways Breeze breeze allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Breeze: from n/a through <= 2.2.21.
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 · moderate confidenceA missing authorization vulnerability in the Cloudways Breeze WordPress caching plugin allows authenticated users to access functionality or data they should not have access to due to incorrectly configured access control security levels. The issue affects all versions up to and including 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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Breeze plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Breeze' in the list. Alternatively, check if the /wp-content/plugins/breeze/ directory exists on the server.Affected if The Breeze plugin is installed and active on the WordPress site
-
Determine installed Breeze versionIn WordPress admin, go to Plugins > Installed Plugins and click on the Breeze plugin to view its version, or inspect the plugin header in the main Breeze PHP file.Affected if The installed version is 2.2.21 or lower (all versions up to and including 2.2.21 are affected)
-
Review WordPress user accountsIn WordPress admin, go to Users > All Users and list all registered user accounts.Affected if There are any authenticated user accounts beyond the primary administrator, particularly users with Editor, Author, Contributor, or Subscriber roles who could potentially exploit the missing authorization
-
Check for excessive user permissionsIn WordPress admin, go to Users > All Users and examine each user's role. In WordPress, go to Users > User Role Editor (if installed) or review the default role capabilities.Affected if Any user has a role that grants more access than necessary, or if lower-privileged users can access Breeze plugin settings or functionality they should not reach
You are affected if the Breeze plugin is installed with version 2.2.21 or lower and there are non-administrative authenticated users on the WordPress site who could access functionality beyond their intended permission level.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to the latest version of the Breeze plugin when a patch is released. In the interim, review user roles and permissions within WordPress and restrict administrative access to trusted personnel only.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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