Mailchimp FormsWordPress extension · Mailmunch
CVE-2024-31378
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in MailMunch MailChimp Forms by MailMunch.This issue affects MailChimp Forms by MailMunch: from n/a through 3.2.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in MailMunch MailChimp Forms plugin versions through 3.2.1 allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.
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
< 3.2.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Confirm MailMunch MailChimp Forms plugin is installedAccess the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'MailMunch' or 'MailChimp Forms' in the plugin listAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the Plugins list, locate the MailMunch MailChimp Forms entry and note the version number displayed below the plugin nameAffected if The version listed is 3.2.1 or earlier (any version less than 3.2.2)
-
Verify the plugin is activeIn the WordPress Plugins admin page, check if the MailMunch MailChimp Forms plugin shows as 'Active' rather than 'Inactive' or 'Deactivated'Affected if The plugin status is Active and the version is less than 3.2.2
-
Confirm authenticated user access existsReview user roles on the site (Users > All Users) to verify there is at least one user account with subscriber-level or higher accessAffected if At least one authenticated user account exists on the WordPress site
You are affected if the MailMunch MailChimp Forms plugin version 3.2.1 or earlier is installed and active on your WordPress site, allowing authenticated users to be targeted by CSRF attacks.
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.
dbcve · scoped3.2.2
Implement anti-CSRF tokens (nonces) for all state-changing operations and validate Origin/Referer headers to ensure requests originate from legitimate sources.
3.2.2
- 1. Back up your WordPress site and database before making any changes
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins > Installed Plugins
- 4. Find the Mailchimp Forms (MailMunch) plugin
- 5. Click Update Now if an update is available, or manually download version 3.2.2 or newer from the WordPress plugin repository
- 6. Verify the updated version number reflects 3.2.2 or higher
- 7. Test that forms and MailChimp integrations continue to function properly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mailchimp Forms
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31378 — 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-31378 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