Is CVE-2026-55234 exploited in the wild?

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

How severe is CVE-2026-55234?

High severity, with a CVSS score of 8.5, published 15 July 2026.

Is there a fix for CVE-2026-55234?

A patch was published on 2026-06-11: Fixed in version 9.37 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55234 attacked?

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

Am I affected by CVE-2026-55234?

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-55234: Wekan broken access control in DDP update rules

CVE-2026-55234 · Severity: high · CVSS 8.5 · Published 2026-07-15

Wekan is an open-source project management tool used by teams to organize tasks on digital boards. A security flaw allows any registered user to move their own tasks, lists, or categories into private boards belonging to other users or teams, even if they are not members of those boards. This could allow an attacker to disrupt operations or inject unauthorized content into sensitive private projects.

Technologies: WeKan. Vendors: WeKan.

Quick answers

Is CVE-2026-55234 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55234 being exploited in the wild.
How severe is CVE-2026-55234?: High severity, with a CVSS score of 8.5, published 15 July 2026.
Which products and versions are affected?: WeKan < 9.37.
Is there a fix for CVE-2026-55234?: A patch was published on 2026-06-11: Fixed in version 9.37 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55234 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55234?: 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

Wekan's DDP (Distributed Data Protocol) update allow rules in 'server/permissions/cards.js', 'lists.js', and 'swimlanes.js' fail to validate the destination 'boardId' during an update operation. The application only checks if the user has write access to the document's current (source) board. An authenticated attacker can use a DDP client to call '/cards/update' (or similar) and use a '$set' modifier to change the 'boardId' to that of a victim's private board. This results in a cross-board write that bypasses board-level membership restrictions. The REST API is not affected as it correctly validates the destination board. The issue is fixed in version 9.37 by implementing a 'deny' rule that rejects updates modifying a 'boardId' to a destination where the user lacks write access.

Affected products

Wekan Wekan < 9.37

Timeline

2026-06-11: patched: Fixed in version 9.37
2026-06-11: advisory: GitHub Security Advisory published
2026-07-15: disclosed: CVE-2026-55234 published to NVD

References

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