CVE-2024-5331: The Breakdance plugin for WordPress is vulnerable to unauthorized access of data in all versions up to, and in

Q: How do I fix CVE-2024-5331?

breakdance: upgrade to 2.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-5331 being exploited?

CVE-2024-5331 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-5331 affect?

CVE-2024-5331 affects breakdance. Severity is medium (CVSS 4.3). The Breakdance plugin for WordPress is vulnerable to unauthorized access of data in all versions up to, and including, 1.7.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to export form submis

Q: How urgent is CVE-2024-5331?

Priority 19/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2024-5331 is a medium-severity flaw (CVSS 4.3) affecting breakdance. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Breakdance plugin for WordPress is vulnerable to unauthorized access of data in all versions up to, and including, 1.7.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to export form submissions.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 86%)
CISA exploited list	No
Weakness	CWE-284, CWE-862
Published	2024-08-01
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: soflyy

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-01 07:15 UTCPublished CVE record published
2026-06-17 08:15 UTCUpdated Record last modified

soflyy breakdance UPGRADE

Affected: < 2.0

Fixed in: 2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy breakdance || rpm -q breakdance || breakdance --version

2. UPGRADE to 2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade breakdance

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade breakdance

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-5331?

breakdance: upgrade to 2.0. Exact commands for each OS are on this page.

Is CVE-2024-5331 being exploited?

CVE-2024-5331 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-5331 affect?

CVE-2024-5331 affects breakdance. Severity is medium (CVSS 4.3). The Breakdance plugin for WordPress is vulnerable to unauthorized access of data in all versions up to, and including, 1.7.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to export form submis

How urgent is CVE-2024-5331?

Priority 19/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-5330 MEDIUM 6.4 UPGRADE The Breakdance plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the breakdance_css_file_p

References

← Back to latest CVEs