CVE-2026-1963VulnerabilityPublished 5 Feb 2026Updated 23 Feb 2026

CVE-2026-1963: WeKan · Improper Access Controls

Affects WeKanSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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 5 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 2026-10-25.

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

1. Upgrade WeKan installations to version 8.21 or later immediately to apply the official patch correcting the access control flaw. 2. Review and restrict network exposure of WeKan instances, limiting access to trusted internal networks or VPNs to reduce remote attack surface. 3. Implement strict access controls and authentication mechanisms around WeKan, including multi-factor authentication, to further protect user accounts. 4. Regularly audit attachment access logs and monitor for unusual access patterns or unauthorized downloads/modifications. 5. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting attachment endpoints. 6. Educate administrators and users about the importance of timely updates and secure handling of attachments. 7. Backup critical project data and attachments regularly to enable recovery in case of data tampering or deletion. 8. Conduct periodic security assessments of WeKan deployments to identify and remediate other potential vulnerabilities.

Description

A vulnerability was found in WeKan up to 8.20. This affects an unknown function of the file models/attachments.js of the component Attachment Storage. The manipulation results in improper access controls. The attack may be launched remotely. Upgrading to version 8.21 mitigates this issue. The patch is identified as c413a7e860bc4d93fe2adcf82516228570bf382d. Upgrading the affected component is advised.

Impact

The vulnerability could allow unauthorized remote attackers to access or manipulate attachments within WeKan, potentially exposing sensitive project files or confidential information. This breach of confidentiality can lead to data leakage, intellectual property theft, or exposure of personal data. Integrity may also be compromised if attackers modify or delete attachments, disrupting workflows and damaging trust in project data. Availability impact is limited but possible if attackers delete or corrupt attachments critical to operations. Since exploitation requires no user interaction or elevated privileges, the attack surface is broad, especially for publicly accessible WeKan instances. Organizations using affected versions risk unauthorized data exposure and operational disruption, which could lead to reputational damage, regulatory penalties, and financial loss. The absence of known exploits reduces immediate risk but does not eliminate the threat, emphasizing the need for timely patching.

Summary

CVE-2026-1963 is an access control vulnerability discovered in WeKan, an open-source kanban board application widely used for project management and collaboration. The vulnerability resides in the Attachment Storage component, specifically within an unspecified function in the models/attachments.js file. Due to improper access control implementation, remote attackers can exploit this flaw to bypass authorization checks and gain unauthorized access to attachments stored within the application. The vulnerability affects all WeKan versions from 8.0 through 8.20. Exploitation does not require user interaction or elevated privileges, increasing the risk of remote compromise. The CVSS 4.0 base score of 5.3 reflects a medium severity, considering the ease of remote exploitation but limited scope and impact. The patch, included in version 8.21, corrects the access control logic to enforce proper authorization on attachment operations. No public exploits or active exploitation have been reported, but the vulnerability poses a risk to confidentiality and integrity of stored attachments, potentially exposing sensitive project data or enabling data tampering. Organizations relying on WeKan for collaboration should upgrade promptly to mitigate this risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:00 UTC

Technical details

References

Community reviews

Related threats