Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-36760: Path Traversal Arbitrary File Write in JeeSite v5.15.1 /a/file/upload

Published Apr 30, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.6Critical · v3.1
EPSS0.38%33rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-36760CWE-22 · Improper Limitation of a Pathname…

CVE-2026-36760 affects JeeSite v5.15.1. The vulnerability is in the fileMd5 parameter of the /a/file/upload endpoint. When chunked upload is enabled, an authenticated attacker who has file upload permissions can manipulate this parameter to perform path traversal and cause uploaded content to be written outside the intended directory. The issue permits arbitrary file write to attacker-chosen filesystem locations, subject to the application's allowed file suffix restrictions.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated low-privilege attacker with upload capability to write arbitrary files with whitelisted extensions to arbitrary locations on the server filesystem. Depending on where files can be written and how those files are subsequently used by the application or host environment, this can lead to unauthorized modification of application data, placement of attacker-controlled files in sensitive paths, disclosure or compromise of sensitive information, and potentially further compromise of the affected system. The provided CVSS vector indicates high confidentiality and integrity impact with no direct availability impact.

Mitigation

If you can’t patch tonight, do this now.

If an official fix is not yet available, disable chunked upload functionality where feasible, or restrict access to the /a/file/upload endpoint to only strictly necessary trusted users. Remove unnecessary file upload permissions, monitor for traversal patterns in fileMd5 and related upload parameters, and enforce filesystem-level permissions so the application account cannot write to sensitive directories. Additional compensating controls include isolating the upload directory, validating canonicalized paths against an allowlisted base directory, and alerting on unexpected file creation in application and web-accessible paths.

Remediation

Patch, then assume compromise.

Upgrade to a fixed JeeSite release if one is available from the vendor. The vulnerable /a/file/upload implementation should be corrected so that the fileMd5 parameter cannot influence filesystem paths outside an intended upload directory. Enforce canonical path validation, reject traversal sequences, generate server-side storage paths independent of user-controlled input, and ensure chunked upload assembly is constrained to a dedicated directory. Review and harden suffix allowlisting so it is not the primary control preventing dangerous writes.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-36760 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2026-36760 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-36760?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2026-36760.
Is there a patch for CVE-2026-36760?
Upgrade to a fixed JeeSite release if one is available from the vendor. The vulnerable /a/file/upload implementation should be corrected so that the fileMd5 parameter cannot influence filesystem paths outside an intended upload directory.
How severe is CVE-2026-36760?
CVE-2026-36760 has a CVSS v3.1 score of 9.6 (Critical) and an EPSS score of 0.38% (33rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.