dbcve.org
MailchimpWordPress extension · Ibericode

CVE-2023-51682

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 4.9.10 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in ibericode MC4WP.This issue affects MC4WP: from n/a through 4.9.9.

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

Missing Authorization vulnerability in ibericode MC4WP (MailChimp for WordPress) plugin. The vulnerability allows unauthorized access to certain functionality due to missing authorization checks. The specific affected function or exploitation vector is not detailed in available documentation.

MitigationApply latest available patch or update to MC4WP beyond version 4.9.9. Review and enforce proper capability checks and nonce validation on sensitive operations within the plugin.

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
MailchimpWordPress extension
Affected:< 4.9.10

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Check installed MC4WP plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'MailChimp for WordPress' (MC4WP) and read the version number displayed. Alternatively, inspect the plugin's main PHP file header in wp-content/plugins/mailchimp-for-wp/ or similar path for the 'Version' tag.
    Affected if The displayed version number is less than 4.9.10, or the version tag in the plugin header reads lower than 4.9.10.
  2. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the MC4WP plugin shows as 'Active'.
    Affected if The plugin is installed and active, and the version is below 4.9.10.
  3. Check for unauthorized admin function access
    Attempt to access MC4WP admin pages or AJAX endpoints directly via URL without being logged in as an administrator, or inspect the plugin's admin-ajax.php handlers and admin menu callbacks for missing capability checks (look for missing current_user_can() calls before sensitive operations).
    Affected if Sensitive plugin functions or admin pages are accessible to unauthenticated users or users lacking proper WordPress capabilities.
  4. Inspect plugin capability configuration
    Review the mc4wp plugin directory for files containing 'capability', 'manage_options', or 'administrator' checks. Compare the code around admin action handlers, form submissions, and API calls to verify each includes proper current_user_can() or nonce validation before executing sensitive operations.
    Affected if Any admin action handler, form processor, or AJAX callback in the plugin lacks capability verification or nonce validation.

The environment is affected if MC4WP version is below 4.9.10 AND the plugin is active, because the missing authorization vulnerability exists in that version range.

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

Apply latest available patch or update to MC4WP beyond version 4.9.9. Review and enforce proper capability checks and nonce validation on sensitive operations within the plugin.

Recommended fix High confidence

MC4WP version 4.9.10

  1. 1. Log in to the WordPress admin dashboard where the MC4WP (Mailchimp for WordPress) plugin is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the MC4WP plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 4.9.10 or later
  5. 5. Alternatively, download the latest version of MC4WP from the official WordPress plugin repository and manually upload/install it

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

Fix this in Mailchimp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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