Wekan up to 10.37 Export models/export.js user._id.toString authToken input validation

Summaryinfo

A vulnerability marked as problematic has been reported in Wekan up to 10.37. The impacted element is the function user._id.toString of the file models/export.js of the component Export Handler. Performing a manipulation of the argument authToken results in input validation. This vulnerability is identified as CVE-2026-68901. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Wekan up to 10.37. This affects the function user._id.toString of the file models/export.js of the component Export Handler. The manipulation of the argument authToken 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 availability. The summary by CVE is:

Wekan is open source kanban built with Meteor. Prior to 10.38, the /api/boards/:boardId/export, /api/boards/:boardId/attachments/:attachmentId/export, /api/boards/:boardId/export/csv, and /api/boards/:boardId/exportExcel handlers in models/export.js and models/exportExcel.js looked up a user from the attacker-controlled authToken query parameter and immediately called user._id.toString() without checking whether ReactiveCache.getUser() returned undefined. A request for a private board with an unknown token therefore threw a TypeError from an asynchronous route, producing an unhandled rejection that could terminate the Wekan process and deny service to all users. Version 10.38 adds a 401 guard after every export token lookup and wraps export handlers with safeRoute() so unexpected exceptions become controlled responses. This issue is fixed in version 10.38.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-68901 since 07/31/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 10.38 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-62714). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Wekan

Version

• 10.0
• 10.1
• 10.2
• 10.3
• 10.4
• 10.5
• 10.6
• 10.7
• 10.8
• 10.9
• 10.10
• 10.11
• 10.12
• 10.13
• 10.14
• 10.15
• 10.16
• 10.17
• 10.18
• 10.19
• 10.20
• 10.21
• 10.22
• 10.23
• 10.24
• 10.25
• 10.26
• 10.27
• 10.28
• 10.29
• 10.30
• 10.31
• 10.32
• 10.33
• 10.34
• 10.35
• 10.36
• 10.37

Website

• Product: https://github.com/wekan/wekan/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion