# CVE-2023-51806: File upload in n/a

> A local attacker can execute arbitrary code by uploading a crafted file to the Ujcms content management system.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-58jj-f9fm-h5qv

## What is CVE-2023-51806?

CVE-2023-51806 is a high-severity vulnerability in n/a, published on 12 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

File Upload vulnerability in Ujcms v.8.0.2 allows a local attacker to execute arbitrary code via a crafted file.

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

## Which versions are affected by CVE-2023-51806?

It affects 1 product.


Products: Ujcms Ujcms.

## How do I fix CVE-2023-51806?

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

## Is CVE-2023-51806 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51350](https://insights.sbomify.com/CVE-2023-51350/): Code injection in n/a (critical 9.8)
- [CVE-2023-34747](https://insights.sbomify.com/CVE-2023-34747/): File upload in n/a (critical 9.8)
- [CVE-2023-34865](https://insights.sbomify.com/CVE-2023-34865/): Path traversal in n/a (critical 9.8)
- [CVE-2023-34878](https://insights.sbomify.com/CVE-2023-34878/): Information disclosure in n/a (high 7.5)
- [CVE-2024-12483](https://insights.sbomify.com/CVE-2024-12483/): Dromara UJCMS User ID id authorization (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51806 and fix it if it is affected.

What it is: CVE-2023-51806 is a high-severity vulnerability in n/a, published on 12 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51806 in the wild and no public exploit code.

Affected product: n/a. 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-2023-51806/ (Markdown: https://insights.sbomify.com/CVE-2023-51806/index.md)
```

## Sources

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

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