dbcve.org
Mailchimp FormsWordPress extension · Mailmunch

CVE-2024-29793

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 3.2.3 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in MailMunch MailChimp Forms by MailMunch allows Stored XSS.This issue affects MailChimp Forms by MailMunch: from n/a through 3.2.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 confidence

A stored cross-site scripting (XSS) vulnerability exists in MailMunch MailChimp Forms plugin versions up to 3.2.2. The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing authenticated attackers to embed malicious JavaScript code that executes in the browsers of other users who view the affected form pages.

MitigationImplement proper input validation and output encoding/sanitization on all form fields that accept user input before rendering content in web pages. Consider using a vetted XSS prevention library and implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

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
Mailchimp FormsWordPress extension
Affected:< 3.2.3

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. Locate the MailMunch MailChimp Forms plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for the 'mailmunch-mailchimp-forms' folder, or view the installed plugins list in the WordPress admin dashboard under Plugins > Installed Plugins
    Affected if The plugin folder or listing exists in your WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (usually mailmunch.php or similar in the plugin folder) and look for the version comment/constant at the top of the file, or check the version displayed in the WordPress admin plugins list
    Affected if The version number found is less than 3.2.3 (for example: 3.2.2, 3.2.1, 3.2.0, or any version below 3.2.3)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the MailMunch MailChimp Forms plugin shows as 'Active'
    Affected if The plugin is activated and running on the site
  4. Check for user-generated form content
    Navigate to the MailMunch plugin settings or form builder in the WordPress admin panel and examine any forms that accept user input or custom field content
    Affected if Any forms are configured that accept and store user-supplied input which could be rendered in web pages

You are affected if the MailMunch MailChimp Forms plugin version is below 3.2.3, the plugin is active, and your site has forms that accept and display user input content.

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

Implement proper input validation and output encoding/sanitization on all form fields that accept user input before rendering content in web pages. Consider using a vetted XSS prevention library and implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

3.2.3

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the MailMunch MailChimp Forms plugin
  4. Check if the current version is below 3.2.3
  5. If vulnerable, click 'Update Now' to upgrade to version 3.2.3
  6. After updating, verify the new version number reflects 3.2.3 or higher
  7. Test the form functionality to ensure the upgrade did not break existing features

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

Fix this in Mailchimp Forms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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