Authenticated file read and DoS via attachment path
Published Jul 15, 2026 · Updated Jul 15, 2026
Path traversal in WeKan before 9.31 allows remote authenticated users to read server files and crash the worker process. The attachment insert rule accepts attacker-controlled versions.original.path and storage values, while the filesystem reader streams that path without checking storage-root containment. Board write access is sufficient; default self-registration exposes the flaw to the lowest legitimate role, with file access limited to the WeKan process account.
Summary
What happened
Path traversal in WeKan before 9.31 allows remote authenticated users to read server files and crash the worker process. The attachment insert rule accepts attacker-controlled versions.original.path and storage values, while the filesystem reader streams that path without checking storage-root containment. Board write access is sufficient; default self-registration exposes the flaw to the lowest legitimate role, with file access limited to the WeKan process account.
The record
- CVE
- CVE-2026-52890
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- WeKan
- Product
- WeKan
- Classifications
- CWE-400, CWE-22, T1005, T1499.004, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 9.31
What conditions does exploitation require?
What is affected?
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 advisory attachment-path reproductionfunctional · validated
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