Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2207: Information Disclosure in WeKan

0
Medium
VulnerabilityCVE-2026-2207cvecve-2026-2207
Published: Sun Feb 08 2026 (02/08/2026, 01:09:38 UTC)
Source: CVE Database V5
Product: WeKan

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/23/2026, 21:07:53 UTC

Technical Analysis

CVE-2026-2207 is a medium severity information disclosure vulnerability affecting the open-source collaborative kanban board application WeKan, specifically versions 8.0 through 8.20. The vulnerability resides in the Activity Publication Handler component, particularly in the processing of the JavaScript file server/publications/activities.js. An attacker can remotely manipulate this component without any authentication or user interaction to disclose sensitive information. The exact nature of the information disclosed is unspecified, but given the component's role in activity publication, it could include user activity data or internal system details. The vulnerability is exploitable over the network with low attack complexity and no privileges required, increasing the risk of unauthorized data exposure. The issue was addressed in WeKan version 8.21 by applying a patch (commit 91a936e07d2976d4246dfe834281c3aaa87f9503) that corrects the processing flaw. No public exploits have been observed, but the ease of exploitation and lack of authentication requirements make timely patching critical. The vulnerability is tracked under CVSS version 4.0 with a score of 6.9, reflecting moderate impact primarily on confidentiality with no impact on integrity or availability.

Potential 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.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-08T01:06:08.704Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6987ee2cf9fa50a62f16ffb4

Added to database: 2/8/2026, 2:00:12 AM

Last enriched: 2/23/2026, 9:07:53 PM

Last updated: 3/26/2026, 11:07:48 AM

Views: 92

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses