# CVE-2026-56028: WordPress Easy Elements for Elementor – Addons & Website Templates plugin <= 1.4.9 - Privilege Escalation vulnerability

> Unauthenticated attackers can escalate privileges in the Easy Elements for Elementor WordPress plugin.

- **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:** 26 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-5j7w-xmv3-fhp4

## What is CVE-2026-56028?

CVE-2026-56028 is a critical vulnerability in themewant Easy Elements for Elementor &#8211; Addons &amp; Website Templates, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Privilege Escalation in Easy Elements for Elementor &#8211; Addons &amp; Website Templates <= 1.4.9 versions.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-56028?


## How do I fix CVE-2026-56028?

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

## Is CVE-2026-56028 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56028 and fix it if it is affected.

What it is: CVE-2026-56028 is a critical vulnerability in themewant Easy Elements for Elementor &#8211; Addons &amp; Website Templates, published on 26 Jun 2026. 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-2026-56028 in the wild and no public exploit code.

Affected product: themewant Easy Elements for Elementor &#8211; Addons &amp; Website Templates. 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-2026-56028/ (Markdown: https://insights.sbomify.com/CVE-2026-56028/index.md)
```

## Sources

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

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