# CVE-2024-24000: File upload in n/a

> Attackers can upload arbitrary files to controllable paths in jshERP due to missing file type validation, potentially leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2024
- **Updated:** 12 Jun 2025
- **Also known as:** GHSA-6xj8-7c6f-w9rq

## What is CVE-2024-24000?

CVE-2024-24000 is a critical vulnerability in n/a, published on 6 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

jshERP v3.3 is vulnerable to Arbitrary File Upload. The jshERP-boot/systemConfig/upload interface does not check the uploaded file type, and the biz parameter can be spliced into the upload path, resulting in arbitrary file uploads with controllable paths.

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

## Which versions are affected by CVE-2024-24000?

It affects 1 product.


Products: Huaxiaerp Jsherp.

## How do I fix CVE-2024-24000?

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

## Is CVE-2024-24000 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-48894](https://insights.sbomify.com/CVE-2023-48894/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24000 and fix it if it is affected.

What it is: CVE-2024-24000 is a critical vulnerability in n/a, published on 6 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-24000 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-2024-24000/ (Markdown: https://insights.sbomify.com/CVE-2024-24000/index.md)
```

## Sources

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

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