Wekan
Wekan: File Upload MIME Type Validation Bypass — Stored XSS via Missing System Binary Fallback
Wekan is open source kanban built with Meteor. Prior to 9.90, isFileValid() in models/fileValidation.js used the Unix file command for content-based MIME detection, but detectMimeFromFile() silently returned undefined when that binary was unavailable and the validation fell back to the attacker-controlled fileObj.type supplied through server/routes/attachmentApi.js. On deployments with WITH_API=true and no file binary, an authenticated board member could label HTML containing JavaScript as image/png, bypass the dangerous MIME check, and store active content under the Wekan origin for execution when another user opened it. Version 9.90 adds looksLikeDangerousMarkup() to inspect file bytes and force dangerous-content scanning when MIME detection is unavailable. This issue is fixed in version 9.90.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 9.90
Fixed in 9.90
Mitigation
Upgrade wekan to 9.90 or later.
References
- Vendor advisory github.com/wekan/wekan/security/advisories/GHS…
- Patch github.com/wekan/wekan/commit/f6ba472f6738bcd3…
- Release notes github.com/wekan/wekan/releases/tag/v9.90
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.