CVE-2026-2208VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2208: WeKan · Missing Authorization

Affects WeKanSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 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 20% 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: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 8 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-26.

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

To mitigate CVE-2026-2208, organizations should immediately upgrade WeKan installations to version 8.21 or later, which contains the official patch addressing the missing authorization issue. Prior to upgrading, review and audit existing rules and permissions within WeKan to identify any suspicious or unauthorized changes. Implement network-level controls to restrict access to WeKan instances, such as IP whitelisting or VPN access, to reduce exposure to remote exploitation. Monitor application logs for unusual activity related to rule modifications or access patterns. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the rules.js endpoint. Regularly review and update access control policies within WeKan to enforce the principle of least privilege. Finally, maintain an incident response plan to quickly address any signs of compromise related to this vulnerability.

Description

A security vulnerability has been detected in WeKan up to 8.20. Impacted is an unknown function of the file server/publications/rules.js of the component Rules Handler. The manipulation leads to missing authorization. The attack can be initiated remotely. Upgrading to version 8.21 is recommended to address this issue. The identifier of the patch is a787bcddf33ca28afb13ff5ea9a4cb92dceac005. The affected component should be upgraded.

Impact

The primary impact of CVE-2026-2208 is unauthorized manipulation of the Rules Handler in WeKan, which could allow attackers to modify or bypass workflow rules, potentially disrupting project management processes or escalating privileges within the application. This could lead to unauthorized data changes, workflow interruptions, or exposure of sensitive project information. Since WeKan is used by organizations for collaborative task and project management, exploitation could compromise operational integrity and confidentiality. The vulnerability’s remote exploitability without authentication increases the risk of automated attacks or exploitation by external threat actors. However, the impact is somewhat limited by the scope of the affected functionality and the absence of known exploits in the wild. Organizations relying on WeKan for critical project management should consider this vulnerability a significant risk to their internal workflows and data integrity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats