# CVE-2023-32243: WordPress Essential Addons for Elementor Plugin 5.4.0-5.7.1 is vulnerable to Privilege Escalation

> An improper authentication flaw in the Essential Addons for Elementor plugin allows attackers to escalate privileges within the WordPress environment.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-4xm5-cg4q-prrp

## What is CVE-2023-32243?

CVE-2023-32243 is a critical vulnerability in Wpdeveloper Essential Addons for Elementor, published on 12 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Authentication vulnerability in WPDeveloper Essential Addons for Elementor allows Privilege Escalation. This issue affects Essential Addons for Elementor: from 5.4.0 through 5.7.1.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Wpdeveloper Essential Addons for Elementor.

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

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

## Is CVE-2023-32243 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32243 exists.

Public exploit code:

- CVE-2023-32243 - Essential Addons for Elementor 5.4.0-5.7.1 - Unauthenticated Privilege Escalation (github_poc): https://github.com/RandomRobbieBF/CVE-2023-32243
- Wordpress CVE-2023-32243 (github_poc): https://github.com/Jenderal92/WP-CVE-2023-32243
- Exploit for CVE-2023-32243 - Unauthorized Account Takeover. (github_poc): https://github.com/gbrsh/CVE-2023-32243
- Identifies domains which run WordPress and tests against vulnerabilities (CVE-2023-32243) / #VU76395 / etc... (github_poc): https://github.com/thatonesecguy/Wordpress-Vulnerability-Identification-Scripts
- poc (github_poc): https://github.com/little44n1o/cve-2023-32243
- https://github.com/manavvedawala2/CVE-2023-32243-proof-of-concept (github_poc): https://github.com/manavvedawala2/CVE-2023-32243-proof-of-concept

## Other vulnerabilities in Wpdeveloper Essential Addons for Elementor

- [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)
- [CVE-2024-8979](https://insights.sbomify.com/CVE-2024-8979/): Information disclosure in Essential Addons for Elementor – Popular Elementor Templates & Widgets (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32243 is a critical vulnerability in Wpdeveloper Essential Addons for Elementor, published on 12 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32243 exists.

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-32243/ (Markdown: https://insights.sbomify.com/CVE-2023-32243/index.md)
```

## Sources

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

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