dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1303

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The MailChimp Campaigns plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.2.4. This is due to missing capability checks on the `mailchimp_campaigns_manager_disconnect_app` function that is hooked to the AJAX action of the same name. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disconnect the site from its MailChimp synchronization app, disrupting automated email campaigns and marketing integrations.

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 confidence

The MailChimp Campaigns WordPress plugin versions up to 3.2.4 lack capability checks on the `mailchimp_campaigns_manager_disconnect_app` AJAX action handler. This allows any authenticated user with Subscriber-level permissions or higher to trigger the disconnect function, severing the site’s connection to MailChimp and breaking automated email campaign synchronization.

MitigationUpdate to version 3.2.5 or later which includes proper authorization checks on the disconnect AJAX action, or apply a patch that adds a capability check (e.g., `manage_options`) before executing the disconnect function.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MailChimp Campaigns plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'MailChimp Campaigns' or 'MailChimp Campaigns for WordPress'. Note the installed version number displayed.
    Affected if Plugin is installed and version shown is 3.2.4 or lower (any version up to and including 3.2.4)
  2. Verify the vulnerable AJAX action exists
    Check the plugin files for the registration of the 'mailchimp_campaigns_manager_disconnect_app' AJAX action. This is typically found in the main plugin PHP file or an includes/ajax file. Look for add_action('wp_ajax_mailchimp_campaigns_manager_disconnect_app', ...)
    Affected if The AJAX action handler 'mailchimp_campaigns_manager_disconnect_app' is registered in the plugin code without a capability check before it
  3. Review the disconnect function for authorization
    Locate the function handling the disconnect action (usually named something like 'disconnect_app' or 'manager_disconnect_app'). Examine the function to see if it includes a capability check such as current_user_can('manage_options') before executing the disconnect logic.
    Affected if The disconnect function executes without first verifying the user has elevated permissions (e.g., manage_options capability)
  4. Test AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=mailchimp_campaigns_manager_disconnect_app while logged in as a Subscriber-level user. A successful response indicates the vulnerability is present.
    Affected if A logged-in user with Subscriber-level access (the lowest privilege role) can successfully trigger the disconnect AJAX action and receive a positive response

You are affected if the MailChimp Campaigns plugin is installed at version 3.2.4 or below AND the disconnect AJAX action can be triggered by users with Subscriber-level permissions without proper capability verification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 3.2.5 or later which includes proper authorization checks on the disconnect AJAX action, or apply a patch that adds a capability check (e.g., `manage_options`) before executing the disconnect function.

Have this fixed 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 help mitigating

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-2026-1303 — 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-2026-1303 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