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

CVE-2026-1897: WeKan · Missing 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 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 26% 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:N/VA:N/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: None
Vulnerable system availability: None
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: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within 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 that addresses the missing authorization issue. 2. Restrict network access to WeKan instances, especially limiting exposure to the internet or untrusted networks, to reduce the attack surface. 3. Implement strict access controls and role-based permissions within WeKan to minimize the number of users with privileges that could be leveraged to exploit this vulnerability. 4. Monitor logs for unusual activity related to position history operations, which could indicate attempted exploitation. 5. Conduct regular security audits and penetration testing focusing on authorization mechanisms in WeKan and other collaboration tools. 6. If upgrading is not immediately feasible, consider applying temporary compensating controls such as web application firewalls (WAF) with rules blocking suspicious requests targeting positionHistory.js endpoints. 7. Educate users about the importance of safeguarding their credentials and limiting privilege escalation opportunities. 8. Stay informed about any emerging exploit reports or additional patches from WeKan developers.

Description

A vulnerability was found in WeKan up to 8.20. Affected by this issue is some unknown functionality of the file server/methods/positionHistory.js of the component Position-History Tracking. The manipulation results in missing authorization. The attack may be performed from remote. Upgrading to version 8.21 can resolve this issue. The patch is identified as 55576ec17722db094835470b386162c9a662fb60. It is advisable to upgrade the affected component.

Impact

The vulnerability could allow unauthorized users with limited privileges to bypass authorization controls and manipulate or access position history data within WeKan. This can lead to unauthorized disclosure of sensitive project management information, such as task movements and history, potentially exposing internal workflows or confidential project details. Additionally, attackers might alter position history records, undermining data integrity and trustworthiness of audit trails. While the vulnerability does not directly impact system availability, the loss of data integrity and confidentiality can disrupt organizational processes and decision-making. For organizations relying heavily on WeKan for project tracking, this could result in operational inefficiencies, compliance issues, and reputational damage. Since the attack can be performed remotely without user interaction, the risk of exploitation is higher in exposed deployments. However, the requirement for some level of privileges limits exploitation to insiders or users with limited access, reducing the scope somewhat. No known active exploitation reduces immediate risk but does not eliminate future threats.

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