CVE-2026-25565: WeKan incorrect authorization in card update API

CVE-2026-25565 · Severity: medium · CVSS 6.5 · Published 2026-02-07

WeKan is an open-source Kanban board application used for task management and project organization. A security flaw in versions prior to 8.19 allows users who should only have "read-only" access to a board to bypass restrictions and modify cards or labels. This could lead to unauthorized changes in project data, task status, or organizational workflows by users who are not supposed to have editing privileges.

Technologies: WeKan. Vendors: WeKan.

Quick answers

Is CVE-2026-25565 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-25565 being exploited in the wild.
How severe is CVE-2026-25565?
Medium severity, with a CVSS score of 6.5, published 7 February 2026.
Which products and versions are affected?
WeKan versions prior to 8.19.
Is there a fix for CVE-2026-25565?
A patch was published on 2025-12-29: Fix commit 181f837d8cbae96bdf9dcbd31beaa3653c2c0285 pushed to GitHub. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-25565 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-25565?
Check whether you run WeKan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An incorrect authorization vulnerability (CWE-863) exists in the WeKan API. The root cause is that certain API endpoints, such as those for updating labels or cards (e.g., PUT /api/boards/:boardId/labels), were using a check for general board access (checkBoardAccess) instead of verifying write permissions (checkBoardWriteAccess). A remote attacker with low-privileged, read-only credentials can exploit this by sending crafted API requests to modify board content. The issue is resolved in WeKan version 8.19 by implementing stricter access control checks in the server-side Meteor code.

Affected products

  • WeKan WeKan versions prior to 8.19

Timeline

  • 2025-12-29: patched: Fix commit 181f837d8cbae96bdf9dcbd31beaa3653c2c0285 pushed to GitHub.
  • 2026-02-07: disclosed: Initial publication of CVE-2026-25565.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.