# CVE-2023-54405: H3C CVM Unauthenticated File Upload via fileUpload/upload Token

> Remote attackers can upload malicious JSP files via an unauthenticated endpoint to achieve remote code execution on H3C CVM.

- **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:** 2 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-369p-hmv2-9pw3

## What is CVE-2023-54405?

CVE-2023-54405 is a critical vulnerability in H3C CVM, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

H3C CVM, the Cloud Virtualization Management component of the H3C CAS cloud platform, contains an unauthenticated arbitrary file upload vulnerability in the /cas/fileUpload/upload endpoint that allows remote attackers to write arbitrary files by manipulating the caller-supplied token parameter without restricting path traversal or file type. Attackers can exploit the path traversal in the token parameter to upload a malicious JSP file into a web-accessible directory and then request it to achieve remote code execution as the web-server user. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.

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

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


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

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

## Is CVE-2023-54405 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54405 is a critical vulnerability in H3C CVM, published on 2 Oct 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-2023-54405 exists.

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

## Sources

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

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