CVE-2024-24000
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedjshERP 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencejshERP v3.3 contains an arbitrary file upload vulnerability in the /systemConfig/upload endpoint. The interface does not validate uploaded file types and allows the 'biz' parameter to be manipulated to control the upload directory path, enabling attackers to upload malicious files to arbitrary server locations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed jshERP versionCheck the application version by accessing the login page, about section, or version file in the deployment directory. Common paths include the login page footer, a /about endpoint, or version configuration files.Affected if The installed version is exactly 3.3 (Huaxiaerp Jsherp)
-
Confirm the /systemConfig/upload endpoint existsAttempt to access the upload endpoint via HTTP GET or check the application's URL routing configuration for the systemConfig controller. The endpoint path is /systemConfig/upload.Affected if The endpoint is accessible and responds to requests, indicating the upload functionality exists in the deployment
-
Verify file type validation is missingInspect the server-side code handling the /systemConfig/upload request, specifically looking for file type validation logic (mime type checks, extension allowlists/blocklists). Check the upload controller's source code.Affected if No file type validation or content-type checking is found in the upload handler code
-
Check 'biz' parameter handling in upload logicReview the upload controller code to see how the 'biz' parameter is processed and whether it is used to construct the file save path without sanitization.Affected if The 'biz' parameter is used directly in file path construction without sanitization or path traversal protection
You are affected if running jshERP version 3.3 with the /systemConfig/upload endpoint exposed and lacking proper file type validation and 'biz' parameter sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict file type whitelist validation, sanitize the 'biz' parameter to prevent path traversal, and store uploaded files outside the web root or in a non-executable directory.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24000 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24000 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data