Is CVE-2026-25563 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-25563 being exploited in the wild.

How severe is CVE-2026-25563?

High severity, with a CVSS score of 7.5, published 7 February 2026.

Is there a fix for CVE-2026-25563?

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-25563 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-25563?

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.

CVE-2026-25563: WeKan IDOR in checklist creation

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

WeKan is an open-source project management tool used to organize tasks on visual boards. A security flaw in versions prior to 8.19 allows users to manipulate task identifiers to create or modify checklists on boards they may not have permission to access. This could lead to unauthorized data modification and disruption of project workflows across different teams or departments.

Technologies: WeKan. Vendors: WeKan.

Quick answers

Is CVE-2026-25563 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-25563 being exploited in the wild.
How severe is CVE-2026-25563?: High severity, with a CVSS score of 7.5, published 7 February 2026.
Which products and versions are affected?: WeKan < 8.19.
Is there a fix for CVE-2026-25563?: 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-25563 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-25563?: 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 Insecure Direct Object Reference (IDOR) vulnerability exists in WeKan's checklist creation and related API routes. The application fails to validate that a provided 'cardId' actually belongs to the specified 'boardId' during request processing. A remote attacker can exploit this by manipulating these identifiers in network requests to perform actions on cards across different boards. This bypasses intended authorization boundaries, allowing for unauthorized checklist modifications. The issue is addressed in version 8.19 by implementing server-side checks to verify card-to-board ownership.

Affected products

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