dbcve.org
BreakdanceWordPress extension · Soflyy

CVE-2024-5330

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 2.0 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
The Breakdance plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the breakdance_css_file_paths_cache parameter in all versions up to, and including, 1.7.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Breakdance WordPress plugin fails to properly sanitize the breakdance_css_file_paths_cache parameter during input and escape it during output, allowing authenticated users with Contributor-level access or higher to inject persistent malicious JavaScript that executes in the browsers of users viewing affected pages.

MitigationUpdate Breakdance to version 1.7.3 or later. Until patched, limit user roles to exclude Contributors and above from accessing affected functionality, and audit existing content for injected scripts.

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
BreakdanceWordPress extension
Affected:< 2.0

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 Breakdance plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Soflyy Breakdance' appears in the list of installed plugins, or query the database: SELECT * FROM wp_options WHERE option_name LIKE '%breakdance%' LIMIT 10
    Affected if Breakdance plugin is not found in the installation
  2. Identify installed Breakdance version
    Check the plugin version listed in WordPress admin > Plugins > Breakdance, or inspect the plugin header in wp-content/plugins/breakdance/plugin.php for the 'Version' comment, or query: SELECT option_value FROM wp_options WHERE option_name = 'breakdance_version'
    Affected if Version is below 2.0 (any 1.x version such as 1.7.2 or earlier)
  3. Check for Contributor-level or higher user accounts
    Query the database: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%' OR meta_value LIKE '%author%' OR meta_value LIKE '%editor%' OR meta_value LIKE '%administrator%'
    Affected if One or more user accounts with Contributor, Author, Editor, or Administrator roles exist in WordPress
  4. Inspect database for suspicious stored scripts
    Search WordPress postmeta and options tables for the breakdance_css_file_paths_cache parameter: SELECT * FROM wp_options WHERE option_name = 'breakdance_css_file_paths_cache'; SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%javascript:%'
    Affected if The breakdance_css_file_paths_cache option contains encoded script tags or suspicious JavaScript payloads, or postmeta records show unexpected script injections in Breakdance-related entries

The environment is affected if Breakdance plugin version is below 2.0, Contributor-level or higher user accounts exist, and the breakdance_css_file_paths_cache parameter in the database contains unsanitized script content or has been modified with malicious payloads.

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 or later
Fixed in 2.0
Interim mitigation

Update Breakdance to version 1.7.3 or later. Until patched, limit user roles to exclude Contributors and above from accessing affected functionality, and audit existing content for injected scripts.

Recommended fix Moderate confidence

Breakdance version 2.0 or later

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find Breakdance in the plugin list.
  5. 5. If an update is available, click 'Update Now' to update to version 2.0 or later.
  6. 6. Alternatively, download the latest version of Breakdance from the official vendor source and upload it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version is 2.0 or higher in Plugins > Installed Plugins.
  8. 8. Test that the Breakdance page builder functions correctly on your site.

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

Fix this in Breakdance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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