CVE-2026-25561: WeKan authorization weakness in attachment upload API

CVE-2026-25561 · Severity: high · CVSS 7.5 · Published 2026-02-07

WeKan, an open-source Kanban board application used for task management, contains a security flaw in how it handles file uploads. The system fails to verify that the specific board, card, and list identifiers provided during an upload actually belong together. This could allow an attacker to upload attachments to cards or boards they should not have access to, potentially leading to data integrity issues or unauthorized file placement within the organization's project management environment.

Technologies: WeKan. Vendors: WeKan.

Quick answers

Is CVE-2026-25561 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-25561 being exploited in the wild.
How severe is CVE-2026-25561?
High severity, with a CVSS score of 7.5, published 7 February 2026.
Which products and versions are affected?
WeKan versions prior to 8.19.
Is there a fix for CVE-2026-25561?
A patch was published on 2026-02-07: Fixed in version 8.19 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-25561 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-25561?
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 authorization weakness (CWE-863) exists in the attachment upload API of WeKan versions prior to 8.19. The root cause is a failure to validate the consistency of provided identifiers, including boardId, cardId, swimlaneId, and listId. An attacker can exploit this by providing mismatched identifiers that do not refer to a coherent card/board relationship, effectively bypassing intended scoping restrictions during file uploads. This allows for the attachment of files to objects outside of the expected organizational hierarchy. The vulnerability is reachable over the network and has been addressed in version 8.19.

Affected products

  • WeKan WeKan versions prior to 8.19

Timeline

  • 2026-02-07: disclosed
  • 2026-02-07: advisory
  • 2026-02-07: patched: Fixed in version 8.19

References

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