Mailchimp for WooCommerce <= 2.7 - Authenticated (Subscriber+) Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 2.7.1
- Affected Plugin
- Mailchimp for WooCommerce
- Affected Version
<= 2.7- CVSS
- 4.3Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2022-2267
At a glance
CVE-2022-2267 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Mailchimp for WooCommerce WordPress plugin, affecting versions <= 2.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.7.1; sites on affected versions should update now. Disclosed August 2022, reported by miguelxpn.
Vulnerability Overview
The plugin Mailchimp for WooCommerce for WordPress is vulnerable to Server-Side Request Forgery via one of its AJAX actions in versions up to, and including, 2.7.1. This makes it possible for an attacker with subscriber privileges or higher to send requests to the internal network.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Mailchimp for WooCommerce <= 2.7 takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Mailchimp for WooCommerce the fix is 2.7.1: builds <= 2.7 are affected, anything from 2.7.1 onward is not.
Remediation
Update to version 2.7.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Mailchimp for WooCommerce 2.7.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Mailchimp for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C