# CVE-2022-40921: File upload in n/a

> An attacker can upload arbitrary files to DedeCMS, potentially leading to remote code execution.

- **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:** 11 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4367-36c5-2mx8

## What is CVE-2022-40921?

CVE-2022-40921 is a high-severity vulnerability in Dedecms Dedecms, published on 11 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

DedeCMS V5.7.99 was discovered to contain an arbitrary file upload vulnerability via the component /dede/file_manage_control.php.

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

## Which versions are affected by CVE-2022-40921?

It affects 1 product.


Products: Dedecms Dedecms.

## How do I fix CVE-2022-40921?

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

## Is CVE-2022-40921 being exploited?

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

## Other vulnerabilities in Dedecms Dedecms

- [CVE-2026-30643](https://insights.sbomify.com/CVE-2026-30643/): Code injection in n/a (critical 9.8)
- [CVE-2026-30694](https://insights.sbomify.com/CVE-2026-30694/): Code injection in n/a (critical 9.8)
- [CVE-2024-35510](https://insights.sbomify.com/CVE-2024-35510/): File upload in n/a (critical 9.8)
- [CVE-2024-35375](https://insights.sbomify.com/CVE-2024-35375/): File upload in n/a (critical 9.8)
- [CVE-2024-29661](https://insights.sbomify.com/CVE-2024-29661/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40921 and fix it if it is affected.

What it is: CVE-2022-40921 is a high-severity vulnerability in Dedecms Dedecms, published on 11 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40921 in the wild and no public exploit code.

Affected product: Dedecms Dedecms. 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-2022-40921/ (Markdown: https://insights.sbomify.com/CVE-2022-40921/index.md)
```

## Sources

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

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