CVE-2024-9210 json
MC4WP: Mailchimp Top Bar <= 1.6.0 - Reflected Cross-Site Scripting
published 2y ago modified 4mo ago also EUVD-2024-49793
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
The MC4WP: Mailchimp Top Bar plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.6.0. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
Patch / fix
- ibericode mailchimp_top_bar 1.6.1
Is CVE-2024-9210 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- dvankooten MC4WP: Mailchimp Top Bar
- dvankootem mailchimp_top_bar
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/b45ba98f-4cd1-406a-8661-e19d5b4c3ba8?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/mailchimp-top-bar/tags/1.6.0/views/settings-page.php#L40
product
-
plugins.trac.wordpress.org
/browser/mailchimp-top-bar/tags/1.6.1/views/settings-page.php#L40
product
Sources
- CVE List CVE-2024-9210
- NVD CVE-2024-9210
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.