# CVE-2024-4605: Breakdance <= 1.7.1 - Authenticated (Contributor+) Remote Code Execution

> Authenticated contributors can execute arbitrary code or escalate privileges in the Breakdance WordPress plugin due to insecure metadata storage.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-j5mg-7pph-vc9m

## What is CVE-2024-4605?

CVE-2024-4605 is a high-severity code injection vulnerability in Breakdance, published on 9 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Breakdance plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.7.1 via post meta data. This is due to the plugin storing custom data in metadata without an underscore prefix. This makes it possible for lower privileged users, such as contributors, to edit this data via UI. As a result they can escalate their privileges or execute arbitrary code.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-4605?


## How do I fix CVE-2024-4605?

No fix has been published for CVE-2024-4605 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-4605 being exploited?

There is no known exploitation of CVE-2024-4605 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4605 and fix it if it is affected.

What it is: CVE-2024-4605 is a high-severity code injection vulnerability in Breakdance, published on 9 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4605 in the wild and no public exploit code.

Affected product: Breakdance. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4605/ (Markdown: https://insights.sbomify.com/CVE-2024-4605/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4605
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4605
- OSV: https://osv.dev/vulnerability/CVE-2024-4605

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4605/
Summaries are generated and may contain mistakes; the official description above is the record.