dbcve.org
BreezeApplication · Cloudways

CVE-2022-29444

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-02
Fix available
A fix is available. Upgrade to 2.0.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Plugin Settings Change leading to Cross-Site Scripting (XSS) vulnerability in Cloudways Breeze plugin <= 2.0.2 on WordPress allows users with a subscriber or higher user role to execute any of the wp_ajax_* actions in the class Breeze_Configuration which includes the ability to change any of the plugin's settings including CDN setting which could be further used for XSS attack.

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 Cloudways Breeze WordPress plugin <= 2.0.2 allows authenticated users with subscriber-level permissions or higher to access wp_ajax_* actions in the Breeze_Configuration class without proper capability checks. This enables low-privilege attackers to modify plugin settings, including CDN configuration, which can be leveraged to inject malicious JavaScript for Cross-Site Scripting (XSS) attacks.

MitigationUpdate the Cloudways Breeze plugin to version 2.0.3 or later, which includes proper capability validation for AJAX actions. Alternatively, implement role-based capability checks (manage_options or similar) on all wp_ajax_* handlers in the Breeze_Configuration class and sanitize all plugin settings outputs.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BreezeApplication
Affected:< 2.0.3

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Confirm Cloudways Breeze plugin is installed
    Navigate to WordPress admin > Plugins or inspect the /wp-content/plugins/ directory for the breeze folder
    Affected if The Cloudways Breeze plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > look for Breeze version number, or read the main plugin file header in /wp-content/plugins/breeze/breeze.php for the Version field
    Affected if The version is less than 2.0.3 (e.g., 2.0.2, 2.0.1, 2.0.0, or any version below 2.0.3)
  3. Verify low-privilege user access to AJAX endpoints
    As a user with subscriber-level role (lowest role), inspect if wp_ajax_breeze_* actions are accessible. Check if the Breeze_Configuration class in includes/class-breeze-configuration.php registers AJAX hooks without capability checks using current_user_can() or a capability validation function
    Affected if AJAX endpoints in the Breeze_Configuration class can be accessed without proper capability verification (no current_user_can('manage_options') or equivalent check)
  4. Inspect CDN configuration settings for unauthorized changes
    Review the WordPress database options table for breeze_cdn* settings or inspect the plugin settings via wp-admin > Breeze > CDN, checking if settings can be modified by a subscriber-level user via AJAX
    Affected if A user with subscriber role can modify CDN configuration settings through plugin AJAX actions

A user is affected if the Cloudways Breeze plugin version is below 2.0.3 AND the site allows authenticated users with subscriber-level permissions to modify plugin settings through exposed AJAX actions.

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
Upgrade available Upgrade to 2.0.3 or later
Fixed in 2.0.3
Interim mitigation

Update the Cloudways Breeze plugin to version 2.0.3 or later, which includes proper capability validation for AJAX actions. Alternatively, implement role-based capability checks (manage_options or similar) on all wp_ajax_* handlers in the Breeze_Configuration class and sanitize all plugin settings outputs.

Recommended fix High confidence

Breeze version 2.0.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to the Plugins section in the left sidebar
  3. Locate the Breeze plugin in the installed plugins list
  4. Click the 'Update now' link or button if an update is available, or manually update to version 2.0.3 or higher
  5. Verify the plugin version after update to confirm version 2.0.3 or later is installed

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

Fix this in Breeze Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29444 — 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-2022-29444 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