Wekan is an open-source kanban-board and project-management application that serves as a self-hosted alternative to proprietary collaboration platforms. Despite a narrow product portfolio focused on the single Wekan application, the project occupies a place among more prominent software offerings in the vulnerability landscape, reflecting its adoption across organizations seeking on-premises team-management tools. Vulnerabilities affecting Wekan recur through access-control and authorization-oriented weakness classes—improper access control, incorrect privilege assignment, incorrect authorization, and exposure of sensitive information—patterns that reflect the application's role managing task visibility and user permissions across shared workspaces. A meaningful share of these disclosures reach serious severity. Defenders deploying Wekan should prioritize access-control and authentication configuration during deployment and updates, and should treat this vendor's advisories as applicable to their specific installation; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Wekan Project over time
Signals from CVEs in this vendor scope (39 CVEs).
39 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-25560CRITICAL WeKan versions prior to 8.19 contain an LDAP filter injection vulnerability in LDAP authentication. User-supplied username input is incorporated into LDAP search filters and DN-rel | Feb 7, 2026 | 9.8 | 32 | NO | NO |
CVE-2026-1963CRITICAL 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 i | Feb 5, 2026 | 9.8 | 30 | NO | NO |
CVE-2026-1962CRITICAL A vulnerability has been found in WeKan up to 8.20. The impacted element is an unknown function of the file server/attachmentMigration.js of the component Attachment Migration. The | Feb 5, 2026 | 9.8 | 30 | NO | NO |
CVE-2026-25859HIGH Wekan versions prior to 8.20 allow non-administrative users to access migration functionality due to insufficient permission checks, potentially resulting in unauthorized migration | Feb 7, 2026 | 8.8 | 29 | NO | NO |
CVE-2026-2206HIGH A security flaw has been discovered in WeKan up to 8.20. This vulnerability affects unknown code of the file server/methods/fixDuplicateLists.js of the component Administrative Rep | Feb 8, 2026 | 8.8 | 27 | NO | NO |
CVE-2026-30845HIGH Wekan is an open source kanban tool built with Meteor. In versions 8.31.0 through 8.33, the board composite publication in Wekan publishes all integration data for a board without | Mar 6, 2026 | 8.2 | 26 | NO | NO |
CVE-2026-25564HIGH WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in checklist creation and related checklist routes. The implementation does not verify that the supp | Feb 7, 2026 | 7.5 | 26 | NO | NO |
CVE-2026-25563HIGH WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in checklist creation and related checklist routes. The implementation does not verify that the supp | Feb 7, 2026 | 7.5 | 26 | NO | NO |
CVE-2026-25561HIGH WeKan versions prior to 8.19 contain an authorization weakness in the attachment upload API. The API does not fully validate that provided identifiers (such as boardId, cardId, swi | Feb 7, 2026 | 7.5 | 26 | NO | NO |
CVE-2025-65781HIGH An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Attachment upload API treats the Authorization bearer value as a userId an | Dec 15, 2025 | 8.2 | 26 | NO | NO |
Signals from CVEs in this vendor scope (39 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Wekan Project.
Media articles that mention a CVE ID that affects a product developed by Wekan Project — matched by CVE ID, not by vendor name.