WeKan up to 8.20 REST API models/checklistItems.js item.cardId/item.checklistId/card.boardId Checklist REST Bleed improper authorization

Summaryinfo

A vulnerability was found in WeKan up to 8.20. It has been declared as critical. Affected is an unknown function of the file models/checklistItems.js of the component REST API. Executing a manipulation of the argument item.cardId/item.checklistId/card.boardId can lead to improper authorization. This vulnerability is handled as CVE-2026-1894. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in WeKan up to 8.20. It has been declared as critical. This vulnerability affects some unknown processing of the file models/checklistItems.js of the component REST API. The manipulation of the argument item.cardId/item.checklistId/card.boardId with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability.

The advisory is available at github.com. This vulnerability was named CVE-2026-1894. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1548.002 by the MITRE ATT&CK project.

Upgrading to version 8.21 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 251d49eea94834cf351bb395808f4a56fb4dbb44 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• WeKan

Version

• 8.0
• 8.1
• 8.2
• 8.3
• 8.4
• 8.5
• 8.6
• 8.7
• 8.8
• 8.9
• 8.10
• 8.11
• 8.12
• 8.13
• 8.14
• 8.15
• 8.16
• 8.17
• 8.18
• 8.19
• 8.20

License

• open-source

Website

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

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.4
NVD Vector: 🔒

CNA Base Score: 6.3
CNA Vector: 🔒

CVSSv2info

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: 🔍

Exploitinginfo

Class: Improper authorization
CWE: CWE-285 / CWE-266
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 Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: WeKan 8.21
Patch: 251d49eea94834cf351bb395808f4a56fb4dbb44

Timelineinfo

02/04/2026 Advisory disclosed
02/04/2026 +0 days VulDB entry created
02/12/2026 +8 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: 251d49eea94834cf351bb395808f4a56fb4dbb44
Status: Confirmed

CVE: CVE-2026-1894 (🔒)
GCVE (CVE): GCVE-0-2026-1894
GCVE (VulDB): GCVE-100-344266

Entryinfo

Created: 02/04/2026 03:51 PM
Updated: 02/12/2026 08:47 AM
Changes: 02/04/2026 03:51 PM (59), 02/05/2026 01:48 PM (30), 02/12/2026 08:47 AM (14)
Complete: 🔍
Submitter: MegaManSec
Cache ID: 244::40

Submitinfo

Accepted

• Submit #742663: Wekan <8.21 IDOR via REST API / improper object relationship validation (by MegaManSec)

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

Do you need the next level of professionalism?

Upgrade your account now!