# CVE-2021-47965: WordPress Plugin WP Super Edit 2.5.4 Unrestricted File Upload

> Attackers can upload arbitrary files via the FCKeditor component to achieve remote code execution and system compromise.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2026
- **Updated:** 25 May 2026
- **Also known as:** GHSA-7wfw-gfch-rf74

## What is CVE-2021-47965?

CVE-2021-47965 is a critical vulnerability in wp-super-edit WP Super Edit, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Plugin WP Super Edit 2.5.4 and earlier contains an unrestricted file upload vulnerability in the FCKeditor component that allows attackers to upload dangerous file types without validation. Attackers can upload arbitrary files through the filemanager upload endpoint to achieve remote code execution and complete system compromise.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2021-47965?


## How do I fix CVE-2021-47965?

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

## Is CVE-2021-47965 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47965 and fix it if it is affected.

What it is: CVE-2021-47965 is a critical vulnerability in wp-super-edit WP Super Edit, published on 15 May 2026. 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-2021-47965 exists.

Affected product: wp-super-edit WP Super Edit. 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-2021-47965/ (Markdown: https://insights.sbomify.com/CVE-2021-47965/index.md)
```

## Sources

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

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