CVE-2025-29012
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 · uneditedMissing Authorization vulnerability in kamleshyadav CF7 7 Mailchimp Add-on CF7-mailchimp-addon allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CF7 7 Mailchimp Add-on: from n/a through < 2.4.
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 · high confidenceThis is a Missing Authorization (Broken Access Control) vulnerability in the kamleshyadav CF7 Mailchimp Add-on WordPress plugin. The plugin fails to properly validate user permissions before allowing access to certain functionality related to Mailchimp integration, allowing unauthorized users to exploit incorrectly configured access control security levels.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm CF7 Mailchimp Add-on plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'CF7 Mailchimp Add-on' by kamleshyadav, or inspect the plugin files in wp-content/plugins/cf7-mailchimp-add-on/ for the main PHP file to check the declared versionAffected if The plugin is installed and active
-
Identify the installed plugin versionOpen the main plugin file (typically cf7-mailchimp-add-on.php) and locate the version comment or Version header in the plugin metadata, or check the version displayed in the WordPress plugins listAffected if Version is lower than 2.4 (or version cannot be determined and the plugin is present)
-
Verify if user registration is enabledIn WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is enabled, or inspect wp_options table for 'users_can_register' option set to 1Affected if User registration is enabled and the site has subscriber-level or other low-privilege users
-
Check if Mailchimp API is configuredNavigate to the CF7 Mailchimp Add-on settings page (typically under Contact Form 7 > Mailchimp) and check if a Mailchimp API key and list are configured, or inspect the plugin's saved options in wp_options for mailchimp-related settingsAffected if Mailchimp API credentials are saved and configured in the plugin
User is affected if the CF7 Mailchimp Add-on plugin version is below 2.4 AND Mailchimp integration is configured AND the site allows low-privilege user access (enabled registration or existing subscribers).
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 · scopedUpdate the CF7 Mailchimp Add-on plugin to version 2.4 or later, which contains proper authorization controls. Verify that role-based access restrictions are enforced for all Mailchimp-related functionality.
version 2.4
- Update the CF7 Mailchimp Add-on plugin to version 2.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29012 — 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-2025-29012 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