# CVE-2021-24216: All-in-One WP Migration < 7.41 - Admin+ Arbitrary File Upload to RCE

> Administrators can upload PHP files to execute arbitrary code due to missing file extension validation in the All-in-One WP Migration plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-29x7-c2jf-9r9c

## What is CVE-2021-24216?

CVE-2021-24216 is a high-severity vulnerability in Unknown All-in-One WP Migration, published on 7 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The All-in-One WP Migration WordPress plugin before 7.41 does not validate uploaded files' extension, which allows administrators to upload PHP files on their site, even on multisite installations.

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

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

It affects 1 product.


Products: Servmask One-Stop Wp Migration.

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

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

## Is CVE-2021-24216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24216 is a high-severity vulnerability in Unknown All-in-One WP Migration, published on 7 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24216 in the wild and no public exploit code.

Affected product: Unknown All-in-One WP Migration. 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-24216/ (Markdown: https://insights.sbomify.com/CVE-2021-24216/index.md)
```

## Sources

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

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