CVE-2026-36762
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 fileEntityId 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.
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 confidenceA path traversal vulnerability in the fileEntityId parameter of the /a/file/upload endpoint in JeeSite v5.15.1 allows authenticated attackers with file upload permissions to write files with whitelisted suffixes to arbitrary filesystem locations by injecting traversal sequences (e.g., ../../../') into the parameter.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 JeeSite installationLook for JeeSite web application artifacts such as the jeesite jar/war file, or check web server logs and application startup scripts for references to JeeSite.Affected if JeeSite is present in the environment
-
Verify JeeSite versionCheck the application's version manifest, About page, or configuration files for the exact version number.Affected if The installed version is JeeSite v5.15.1
-
Confirm /a/file/upload endpoint existsProbe the application for the existence of the /a/file/upload endpoint by reviewing application routing configuration or attempting a request to the endpoint.Affected if The /a/file/upload endpoint is accessible
-
Check if file upload permission is enabledReview user role permissions and file upload module configuration to determine if any authenticated users have file upload privileges.Affected if File upload permissions are granted to any user role
-
Inspect fileEntityId parameter validationAnalyze the backend code or intercept requests to the /a/file/upload endpoint and examine how the fileEntityId parameter is processed for path traversal characters.Affected if The fileEntityId parameter lacks path traversal validation (allows ../ sequences)
A user is affected if they are running JeeSite v5.15.1 with the /a/file/upload endpoint accessible and file upload permissions enabled, and the fileEntityId parameter does not sanitize path traversal sequences.
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 input validation on the fileEntityId parameter to reject path traversal sequences, enforce canonicalization checks to resolve paths before validation, and restrict file write operations to the designated upload directory only.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.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,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36762 — 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-36762 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