MC4WP: Mailchimp for WordPress Security & Risk Analysis

The Mailchimp for WordPress plugin (v4.12.0) exhibits a mixed security posture. While there are no currently unpatched CVEs and the plugin doesn't bundle external libraries, significant concerns arise from its static analysis. A notable attack surface exists with 2 unprotected entry points: 1 AJAX handler and 1 REST API route lacking permission callbacks. This directly exposes functionalities to unauthorized access and potential manipulation. Furthermore, only 41% of output is properly escaped, suggesting a heightened risk of Cross-Site Scripting (XSS) vulnerabilities. The presence of 4 total SQL queries with only 25% using prepared statements indicates a risk of SQL injection. Taint analysis shows 4 flows with unsanitized paths, which, although not flagged as critical or high, combined with other weaknesses, warrants caution.

The plugin's historical vulnerability data reveals a pattern of past issues, including missing authorization, XSS, CSRF, and open redirects. The sheer volume of 11 known CVEs, even if all are patched, suggests a history of security weaknesses in the codebase. The fact that the last vulnerability was in 2026 (presumably a typo and should be a past year) is concerning if it implies recent discovery of unpatched issues or a lack of ongoing security vigilance. In conclusion, while the absence of unpatched vulnerabilities is a positive sign, the unprotected entry points, insufficient output escaping, and the plugin's vulnerability history present substantial risks that require careful consideration and mitigation.