CVE-2026-36760
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 · uneditedAn issue in the fileMd5 parameter in the /a/file/upload endpoint of JeeSite v5.15.1 allows authenticated attackers with file upload permissions to execute a path traversal and write arbitrary files with whitelisted suffixes to arbitrary filesystem locations while chunked upload is enabled.
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 · moderate confidenceA path traversal vulnerability in JeeSite v5.15.1 allows authenticated attackers with file upload permissions to write arbitrary files to unintended filesystem locations via the fileMd5 parameter in the /a/file/upload endpoint when chunked upload is enabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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.
-
Confirm JeeSite is installedCheck your web applications directory or application metadata for JeeSite. Look for jeesite or similar naming in deployed artifacts, configuration files, or the application banner.Affected if JeeSite is not present in your environment
-
Identify the installed JeeSite versionLocate the version information in the JeeSite deployment - typically found in pom.xml, version.properties, or the management console. Compare against the affected version (v5.15.1).Affected if The installed version matches or is within the affected version range (v5.15.1 and related versions)
-
Determine if chunked upload is enabledInspect the application configuration files (such as application.yml, application.properties, or jeesite-config.xml) for settings related to chunked or multipart upload. Look for properties like 'chunkedUpload', 'enableChunked', or 'multipart' configuration with chunking enabled.Affected if Chunked upload functionality is enabled in the configuration
-
Verify the /a/file/upload endpoint exists and is accessibleCheck if the /a/file/upload endpoint is exposed in your JeeSite deployment. Review your web.xml or security configuration for URL mappings, and confirm the endpoint responds to requests.Affected if The /a/file/upload endpoint is accessible and accepts requests
-
Confirm file upload permissions are granted to usersReview the user role and permission configuration in JeeSite's admin panel or database. Check if any role assigned to users includes 'file:upload' or file upload permissions.Affected if Users with access have file upload permissions assigned
Your environment is affected if JeeSite is running the vulnerable version (v5.15.1) WITH chunked upload enabled AND the upload endpoint is accessible to users with file upload permissions.
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 dataDisable chunked upload if not required, implement strict input validation on the fileMd5 parameter to reject path traversal sequences (../), and apply vendor patches.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36760 — 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-2026-36760 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