# CVE-2026-6443: Essentialplugin Plugins (Various Versions) - Injected Backdoor

> A malicious actor embedded backdoors in multiple Essentialplugin WordPress plugins, allowing persistent access and spam injection on affected sites.

- **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:** 17 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-c8jg-hc58-jrx2

## What is CVE-2026-6443?

CVE-2026-6443 is a critical vulnerability in essentialplugin Accordion and Accordion Slider, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All plugins by Essentialplugin for WordPress are vulnerable to an injected backdoor in various versions. This is due to the plugin being sold to a malicious threat actor that embedded a backdoor in all of the plugin's they acquired. This makes it possible for the threat actor to maintain a persistent backdoor and inject spam into the affected sites.

Weakness: CWE-506 (Embedded Malicious Code)

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


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

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

## Is CVE-2026-6443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6443 is a critical vulnerability in essentialplugin Accordion and Accordion Slider, published on 17 Apr 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-6443 in the wild and no public exploit code.

Affected product: essentialplugin Accordion and Accordion Slider. 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-6443/ (Markdown: https://insights.sbomify.com/CVE-2026-6443/index.md)
```

## Sources

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

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