Wekan up to 9.89 File Validation models/fileValidation.js detectMimeFromFile Type input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Wekan up to 9.89 and classified as critical. The affected element is the function detectMimeFromFile of the file models/fileValidation.js of the component File Validation. Performing a manipulation of the argument Type results in input validation.
This vulnerability was named CVE-2026-68899. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Wekan up to 9.89. It has been classified as critical. This affects the function detectMimeFromFile of the file models/fileValidation.js of the component File Validation. The manipulation of the argument type with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-68899 since 07/31/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 9.90 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 9.0
- 9.1
- 9.2
- 9.3
- 9.4
- 9.5
- 9.6
- 9.7
- 9.8
- 9.9
- 9.10
- 9.11
- 9.12
- 9.13
- 9.14
- 9.15
- 9.16
- 9.17
- 9.18
- 9.19
- 9.20
- 9.21
- 9.22
- 9.23
- 9.24
- 9.25
- 9.26
- 9.27
- 9.28
- 9.29
- 9.30
- 9.31
- 9.32
- 9.33
- 9.34
- 9.35
- 9.36
- 9.37
- 9.38
- 9.39
- 9.40
- 9.41
- 9.42
- 9.43
- 9.44
- 9.45
- 9.46
- 9.47
- 9.48
- 9.49
- 9.50
- 9.51
- 9.52
- 9.53
- 9.54
- 9.55
- 9.56
- 9.57
- 9.58
- 9.59
- 9.60
- 9.61
- 9.62
- 9.63
- 9.64
- 9.65
- 9.66
- 9.67
- 9.68
- 9.69
- 9.70
- 9.71
- 9.72
- 9.73
- 9.74
- 9.75
- 9.76
- 9.77
- 9.78
- 9.79
- 9.80
- 9.81
- 9.82
- 9.83
- 9.84
- 9.85
- 9.86
- 9.87
- 9.88
- 9.89
Website
- Product: https://github.com/wekan/wekan/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.0
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.7
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Wekan 9.90
Timeline
07/31/2026 CVE reserved08/19/2026 Advisory disclosed
08/19/2026 VulDB entry created
08/19/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-68899 (🔒)
GCVE (CVE): GCVE-0-2026-68899
GCVE (VulDB): GCVE-100-393333
Entry
Created: 08/19/2026 21:49Changes: 08/19/2026 21:49 (66)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.