CVE-2026-23693: ElementsKit Elementor Addons < 3.7.9 Unauthenticated Mailchimp REST Endpoint
ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor (elementskit-lite) WordPress plugin versions prior to 3.7.9 expose the REST endpoint /wp-json/elementskit/v1/widget/mailchimp/subscribe without authentication. The endpoint accepts client-supplied Mailchimp API credentials and insufficiently validates certain parameters, including the list parameter, when constructing upstream Mailchimp API requests. An unauthenticated attacker can abuse the endpoint as an open proxy to Mailchimp, potentially triggering unauthorized API calls, manipulating subscription data, exhausting API quotas, or causing resource consumption on the affected WordPress site.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ElementsKit Elementor Addons (elementskit-lite) WordPress pluginto a version that resolves this vulnerability.Fixed in 3.7.9 - Compensating control
Restrict access to the WordPress REST endpoint /wp-json/elementskit/v1/widget/mailchimp/subscribe (e.g., via firewall/WAF/ACL) so unauthenticated clients cannot reach it and use it as an open proxy.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23693?
CVE-2026-23693 is classified as a high severity vulnerability due to its potential impact on unauthorized access to sensitive data.
How do I fix CVE-2026-23693?
To fix CVE-2026-23693, update the ElementsKit Lite plugin to version 3.7.9 or newer to secure the REST endpoint.
What is the impact of CVE-2026-23693?
CVE-2026-23693 allows unauthorized users to access and misuse the Mailchimp API credentials via an unsecured REST endpoint.
Is CVE-2026-23693 present in all versions of ElementsKit Lite?
CVE-2026-23693 affects all versions of ElementsKit Lite prior to version 3.7.9.
What should I do if I cannot update from an affected version of ElementsKit Lite due to compatibility issues?
If you cannot update due to compatibility issues, consider disabling the affected REST API endpoint or implementing additional access controls until an update is feasible.