CVE-2024-31390
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: Improper Control of Generation of Code ('Code Injection') vulnerability in Soflyy Breakdance allows : Code Injection.This issue affects Breakdance: from n/a through 1.7.2.
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 confidenceImproper Control of Generation of Code (Code Injection) vulnerability in Soflyy Breakdance WordPress page builder plugin allows attackers to inject and execute arbitrary code. The vulnerability affects all versions through 1.7.2. This is a critical server-side code injection flaw that can lead to complete site compromise.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
-
Locate the Breakdance plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'breakdance' or 'breakdance-builder'. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';Affected if The plugin folder exists in wp-content/plugins/ or the plugin is listed in active_plugins
-
Determine the installed Breakdance versionRead the main plugin file header in wp-content/plugins/breakdance/plugin.php or wp-content/plugins/breakdance/breakdance.php for the 'Version:' comment. Alternatively, query: SELECT option_value FROM wp_options WHERE option_name = 'breakdance_version';
-
Compare the version against affected rangeAffected if The installed version is 1.7.2 or any earlier version (1.0 through 1.7.2 are all affected)
-
Identify plugin endpoints potentially targetedCheck for PHP files in the plugin directory, particularly any files handling form submissions, imports, or template processing. Common paths: wp-content/plugins/breakdance/includes/ or wp-content/plugins/breakdance/inc/Affected if The plugin directory contains files that process user input server-side (this is true for all installations)
-
Review access logs for exploitation indicatorsSearch web server access logs (Apache, Nginx) for requests to Breakdance plugin paths containing suspicious patterns such as: base64_decode, eval, system, shell_exec, or unusual POST data to /wp-content/plugins/breakdance/* endpointsAffected if Logs show requests to plugin endpoints with code injection patterns or unexpected PHP function calls
A system is affected if the Breakdance plugin is installed and the installed version is 1.7.2 or lower, since all versions through 1.7.2 contain the code injection vulnerability.
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 Breakdance version immediately. If no patched version is available, disable the plugin or deploy WAF rules to block suspicious requests targeting plugin endpoints. Review access logs for indicators of compromise.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31390 — 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-2024-31390 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