VulnerabilityPublished 4 Feb 2026Updated 23 Feb 2026

CVE-2026-1894: WeKan · Improper Authorization

Affects WeKanSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 8.21 : update WeKan when convenient.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.21

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
WeKan	Affected =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	Fixed in–
GitHubwekan/wekan`pkg:github/wekan/wekan`Other threats	Affected =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	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade WeKan installations to version 8.21 or later, where the authorization logic has been fixed. Until upgrade is possible, organizations should restrict network access to the WeKan REST API to trusted users and networks only, using firewalls or VPNs. Implement strict role-based access controls and monitor API usage logs for unusual access patterns involving checklist items or cards. Conduct regular audits of user permissions to ensure least privilege principles are enforced. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious parameter manipulations targeting item.cardId, item.checklistId, or card.boardId. Educate administrators and users about the importance of timely patching and monitoring for anomalous activity. Finally, maintain backups of critical project data to enable recovery in case of unauthorized modifications.

Description

A vulnerability was detected in WeKan up to 8.20. This impacts an unknown function of the file models/checklistItems.js of the component REST API. Performing a manipulation of the argument item.cardId/item.checklistId/card.boardId results in improper authorization. Remote exploitation of the attack is possible. Upgrading to version 8.21 will fix this issue. The patch is named 251d49eea94834cf351bb395808f4a56fb4dbb44. Upgrading the affected component is recommended.

Impact

The vulnerability allows attackers with low privileges to access or modify checklist items and cards they should not have access to, potentially leading to unauthorized disclosure of sensitive project information, unauthorized changes to task statuses, or disruption of project workflows. This can undermine data integrity and confidentiality within teams using WeKan, especially in environments where sensitive or proprietary information is managed. Since WeKan is often deployed in enterprise, educational, and governmental contexts for collaborative project management, exploitation could lead to insider threat scenarios or lateral movement within networks. The remote exploitability and lack of user interaction make it easier for attackers to leverage this flaw at scale. While the impact is moderate, organizations with strict data governance or compliance requirements may face regulatory or reputational risks if unauthorized access occurs.

Summary

CVE-2026-1894 is an improper authorization vulnerability discovered in the WeKan open-source kanban board application, affecting all versions up to 8.20. The vulnerability exists in the REST API, specifically within the models/checklistItems.js file. Attackers can manipulate key parameters—item.cardId, item.checklistId, and card.boardId—to bypass authorization checks improperly implemented in the API. This allows an attacker with limited privileges to perform unauthorized actions on checklist items or cards belonging to other users or boards. The flaw does not require user interaction and can be exploited remotely over the network. The vulnerability arises from insufficient validation of ownership or access rights when processing these identifiers, leading to unauthorized access or modification of data. The issue is resolved in version 8.21 by correcting the authorization logic. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no user interaction (UI:N), and privileges required are low (PR:L). The impact on confidentiality, integrity, and availability is limited but present (VC:L, VI:L, VA:L). No public exploits have been reported yet, but the vulnerability is significant for organizations relying on WeKan for task and project management.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:59 UTC

Technical details

References

Community reviews

Related threats