Arbitrary file write via unsanitized fileMd5 path
Published Apr 30, 2026 · Updated Apr 30, 2026
Path traversal in JeeSite 5.15.1 and earlier allows remote authenticated users to write whitelisted file types to arbitrary paths. The chunked upload code concatenates the unsanitized fileMd5 value into a temporary-file path and returns before content-type validation when chunks remain. File-upload permission and file.chunked=true are required; the resulting write is limited to whitelisted suffixes but can target arbitrary filesystem locations.
Summary
What happened
Path traversal in JeeSite 5.15.1 and earlier allows remote authenticated users to write whitelisted file types to arbitrary paths. The chunked upload code concatenates the unsanitized fileMd5 value into a temporary-file path and returns before content-type validation when chunks remain. File-upload permission and file.chunked=true are required; the resulting write is limited to whitelisted suffixes but can target arbitrary filesystem locations.
The record
- CVE
- CVE-2026-36760
- Published
- Apr 30, 2026
- Updated
- Apr 30, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 30, 2026CVE publishedPublication date reported by the CVE source.
- Apr 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 530 reproduction procedureproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo