Authenticated command injection via scanner filename
Published Aug 19, 2026 · Updated Aug 19, 2026
Command injection in WeKan before 9.75 allows remote authenticated users to execute commands via a crafted attachment filename. In models/fileValidation.js, the external scanner path replaces {file} in the administrator-set externalCommandLine with fileObj.path and passes the result to asyncExec, which invokes /bin/sh -c; double quotes do not stop $() or backtick expansion. Reachability requires an authenticated account that can upload attachments and an external scanner configuration, and successful exploitation runs as the WeKan server process.
Summary
What happened
Command injection in WeKan before 9.75 allows remote authenticated users to execute commands via a crafted attachment filename. In models/fileValidation.js, the external scanner path replaces {file} in the administrator-set externalCommandLine with fileObj.path and passes the result to asyncExec, which invokes /bin/sh -c; double quotes do not stop $() or backtick expansion. Reachability requires an authenticated account that can upload attachments and an external scanner configuration, and successful exploitation runs as the WeKan server process.
The record
- CVE
- CVE-2026-68560
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- WeKan
- Product
- WeKan
- Classifications
- CWE-78, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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.75
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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