MC4WP: Mailchimp for WordPress Vulnerability (Medium) – CVE-2026-1781

MC4WP: Mailchimp for WordPress Vulnerability (Medium) – CVE-2026-1781

by | Mar 10, 2026 | Plugins

Attack Vectors

MC4WP: Mailchimp for WordPress (slug: mailchimp-for-wp) is affected by CVE-2026-1781, a Medium severity issue (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L). In versions up to and including 4.11.1, an attacker can submit a crafted web request directly to your site (no login required) that causes the plugin’s form handler to perform an unsubscribe action instead of a subscribe.

The attack relies on the plugin trusting a POST parameter named _mc4wp_action without proper validation. Because the form ID is publicly exposed in the page HTML source, an unauthenticated attacker who can discover that ID can attempt to trigger unsubscribe processing and remove email addresses from your connected Mailchimp audience.

Security Weakness

The underlying weakness is missing authorization: the plugin allows unauthenticated requests to influence what action the form processing performs. Specifically, it trusts the _mc4wp_action POST parameter, enabling a request to force an unsubscribe workflow.

From a business perspective, this is not about data theft; it’s about unauthorized changes to marketing operations. The integrity of your subscription process can be manipulated externally, even by someone who is not a registered WordPress user.

Technical or Business Impacts

List integrity and revenue risk: Unauthorized, arbitrary unsubscriptions can shrink your addressable audience and directly reduce campaign reach, lead volume, and conversion opportunities. If triggered repeatedly, it can undermine confidence in reporting (subscriber counts, attribution, lifecycle performance) and complicate forecasting for marketing and sales.

Operational disruption: Teams may spend time investigating “mysterious” churn, troubleshooting form performance, reconciling Mailchimp audience changes, and running re-permission or re-acquisition efforts—costing budget and time.

Compliance and customer trust considerations: While this vulnerability is not described as exposing personal data, it can still create compliance headaches if opt-in records are unexpectedly altered and you cannot clearly explain why contacts were removed. This may also impact customer experience if legitimate subscribers stop receiving important communications.

Recommended remediation: Update MC4WP: Mailchimp for WordPress to version 4.12.0 or newer, which includes a patch for this issue. Reference: CVE-2026-1781 and the vendor analysis/source: Wordfence vulnerability record.

Similar Attacks

Vulnerabilities that allow unauthorized actions (especially without login) are commonly exploited to disrupt business processes rather than steal data. A few widely documented examples include:

Kaseya VSA supply-chain attack (REvil) – CISA Advisory (attackers leveraged a management platform to disrupt operations at scale).

Ryuk ransomware campaigns – CISA/FBI Alert (operational disruption and business downtime as a primary outcome).

Mirai botnet (large-scale abuse of exposed systems leading to service disruption).

Vantage Vulnerability (Medium) – CVE-2026-5070

Attack Vectors CVE-2026-5070 is a Medium severity vulnerability (CVSS 6.4) affecting the Vantage WordPress theme (slug: vantage) in versions up to and including 1.20.32. It enables authenticated users with Contributor access or higher to inject malicious script into a...

WP Docs Vulnerability (Medium) – CVE-2026-3878

Attack Vectors CVE-2026-3878 is a Medium severity Stored Cross-Site Scripting (XSS) vulnerability (CVSS 6.4) affecting the WP Docs WordPress plugin (wp-docs) in versions 2.2.9 and below. The issue is exploitable by an authenticated user with Subscriber-level access or...

WPFore Subscribers