Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12172: CWE-352 Cross-Site Request Forgery (CSRF) in mailchimp Mailchimp List Subscribe Form

0
Medium
VulnerabilityCVE-2025-12172cvecve-2025-12172cwe-352
Published: Thu Feb 19 2026 (02/19/2026, 03:25:12 UTC)
Source: CVE Database V5
Vendor/Project: mailchimp
Product: Mailchimp List Subscribe Form

Description

The Mailchimp List Subscribe Form plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.0. This is due to missing or incorrect nonce validation on the mailchimp_sf_change_list_if_necessary() function. This makes it possible for unauthenticated attackers to change Mailchimp lists via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 02/19/2026, 04:29:58 UTC

Technical Analysis

CVE-2025-12172 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the Mailchimp List Subscribe Form plugin for WordPress, affecting all versions up to and including 2.0.0. The vulnerability stems from the absence or improper implementation of nonce validation in the mailchimp_sf_change_list_if_necessary() function. Nonces are security tokens used to verify that requests originate from legitimate users and not from malicious third parties. Without proper nonce checks, an attacker can craft a malicious web request that, if executed by an authenticated site administrator (e.g., by clicking a link), can alter Mailchimp list configurations without the administrator's consent. This attack vector requires no authentication on the attacker’s part but does require user interaction from a privileged user. The vulnerability impacts the integrity of the Mailchimp list data by allowing unauthorized changes, potentially disrupting marketing campaigns or causing data inconsistencies. The CVSS v3.1 base score is 4.3 (medium), reflecting the limited impact on confidentiality and availability, the ease of exploitation, and the requirement for user interaction. No public exploits have been reported to date, but the vulnerability remains a risk for sites using this plugin. The lack of a patch link indicates that a fix may not yet be publicly available, emphasizing the need for interim mitigations.

Potential Impact

For European organizations, this vulnerability primarily threatens the integrity of marketing and subscriber data managed through Mailchimp lists on WordPress sites. Unauthorized changes to subscriber lists could lead to misdirected communications, loss of subscriber trust, or disruption of marketing workflows. While confidentiality and availability are not directly impacted, the manipulation of list data could indirectly affect business operations and reputation. Organizations relying heavily on digital marketing and customer engagement via Mailchimp integrated with WordPress are at higher risk. Additionally, if attackers leverage this vulnerability in targeted phishing campaigns, it could facilitate broader social engineering attacks. The requirement for administrator interaction means that organizations with strong user awareness and phishing defenses may reduce risk, but those without such measures remain vulnerable. The medium severity score suggests that while the threat is not critical, it should not be ignored, especially in sectors where marketing data integrity is crucial.

Mitigation Recommendations

1. Monitor for and apply updates from the Mailchimp List Subscribe Form plugin vendor as soon as patches become available. 2. Until a patch is released, implement custom nonce validation in the mailchimp_sf_change_list_if_necessary() function or use Web Application Firewalls (WAFs) to detect and block suspicious CSRF attempts targeting this endpoint. 3. Educate WordPress site administrators about the risks of clicking unsolicited links, especially those that could trigger administrative actions. 4. Limit administrative privileges to only necessary personnel and consider multi-factor authentication (MFA) to reduce the risk of compromised accounts. 5. Regularly audit Mailchimp list configurations and logs for unauthorized changes to detect potential exploitation early. 6. Employ Content Security Policy (CSP) headers and SameSite cookie attributes to reduce the risk of CSRF attacks. 7. Consider temporarily disabling or restricting the vulnerable plugin functionality if feasible until a patch is available.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-24T14:55:13.389Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69968d636aea4a407a3900d5

Added to database: 2/19/2026, 4:11:15 AM

Last enriched: 2/19/2026, 4:29:58 AM

Last updated: 2/21/2026, 12:18:23 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats