# CVE-2023-3779: Essential Addons For Elementor <=5.8.1 - Unauthenticated MailChimp API Key Disclosure

> Unauthenticated attackers can obtain MailChimp API keys from page source code in the Essential Addons for Elementor plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-f2q2-5ww5-3fjg

## What is CVE-2023-3779?

CVE-2023-3779 is a medium-severity vulnerability in Wpdeveloper Essential Addons for Elementor, published on 20 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Essential Addons For Elementor plugin for WordPress is vulnerable to unauthenticated API key disclosure in versions up to, and including, 5.8.1 due to the plugin adding the API key to the source code of any page running the MailChimp block. This makes it possible for unauthenticated attackers to obtain a site's MailChimp API key. We recommend resetting any MailChimp API keys if running a vulnerable version of this plugin with the MailChimp block enabled as the API key may have been compromised. This only affects sites running the premium version of the plugin and that have the Mailchimp block enabled on a page.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-3779?

It affects 1 product.


Products: Wpdeveloper Essential Addons for Elementor.

## How do I fix CVE-2023-3779?

No fix has been published for CVE-2023-3779 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-3779 being exploited?

There is no known exploitation of CVE-2023-3779 in the wild and no public exploit code.

## Other vulnerabilities in Wpdeveloper Essential Addons for Elementor

- [CVE-2023-32243](https://insights.sbomify.com/CVE-2023-32243/): WordPress Essential Addons for Elementor Plugin 5.4.0-5.7.1 is vulnerable to Privilege Escalation (critical 9.8)
- [CVE-2022-0320](https://insights.sbomify.com/CVE-2022-0320/): Essential Addons for Elementor < 5.0.5 - Unauthenticated LFI (critical 9.8)
- [CVE-2021-4447](https://insights.sbomify.com/CVE-2021-4447/): Essential Addons for Elementor <= 4.6.4 - Authenticated (Contributor+) Privilege Escalation (high 8.8)
- [CVE-2023-41955](https://insights.sbomify.com/CVE-2023-41955/): WordPress Essential Addons for Elementor plugin <= 5.8.8 - Contributor+ Privilege Escalation vulnerability (high 8.8)
- [CVE-2024-3018](https://insights.sbomify.com/CVE-2024-3018/): Essential Addons for Elementor <= 5.9.13 - Authenticated (Author+) PHP Object Injection via error_resetpassword (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3779 and fix it if it is affected.

What it is: CVE-2023-3779 is a medium-severity vulnerability in Wpdeveloper Essential Addons for Elementor, published on 20 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3779 in the wild and no public exploit code.

Affected product: Wpdeveloper Essential Addons for Elementor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-3779/ (Markdown: https://insights.sbomify.com/CVE-2023-3779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3779
- OSV: https://osv.dev/vulnerability/CVE-2023-3779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3779/
Summaries are generated and may contain mistakes; the official description above is the record.