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

CVE-2026-2207: WeKan · Information Disclosure

Affects WeKanSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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-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

To mitigate CVE-2026-2207, organizations should immediately upgrade all affected WeKan instances to version 8.21 or later, which contains the official patch addressing the vulnerability. If immediate upgrading is not feasible, organizations should restrict network access to WeKan servers by implementing firewall rules or VPN requirements to limit exposure to trusted users only. Monitoring and logging access to the Activity Publication Handler component may help detect suspicious activity indicative of exploitation attempts. Additionally, reviewing and minimizing the amount of sensitive information stored or processed in WeKan can reduce potential impact. Regularly auditing WeKan deployments for outdated versions and applying security updates promptly is critical. Finally, organizations should consider isolating WeKan instances from public internet access unless absolutely necessary and enforce strong access controls to reduce attack surface.

Description

A weakness has been identified in WeKan up to 8.20. This issue affects some unknown processing of the file server/publications/activities.js of the component Activity Publication Handler. Executing a manipulation can lead to information disclosure. It is possible to launch the attack remotely. Upgrading to version 8.21 is capable of addressing this issue. This patch is called 91a936e07d2976d4246dfe834281c3aaa87f9503. You should upgrade the affected component.

Impact

The primary impact of CVE-2026-2207 is unauthorized information disclosure, which can compromise the confidentiality of sensitive data managed or processed by WeKan instances. Organizations relying on WeKan for project management and collaboration may risk exposure of internal activity logs, user actions, or other sensitive operational data. This could lead to privacy violations, competitive intelligence gathering by adversaries, or facilitation of further attacks if sensitive system information is leaked. Since exploitation requires no authentication or user interaction, any publicly accessible WeKan deployment running affected versions is at risk. The scope includes all organizations using WeKan versions 8.0 through 8.20, particularly those with internet-facing instances. Although no known exploits are currently active in the wild, the vulnerability's characteristics suggest a moderate risk of exploitation, especially in environments with lax network controls or where WeKan is exposed to untrusted networks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats