CVE-2026-55234: Wekan: Broken access control: any authenticated user can move their Cards/Lists/Swimlanes into a private board they are not a member of (cross-board write via collection allow rule)
Wekan is open source kanban built with Meteor. Prior to 9.37, Wekan DDP update allow rules in server/permissions/cards.js, server/permissions/lists.js, and server/permissions/swimlanes.js authorize against the stored source boardId and do not validate a new boardId in the update modifier. Any authenticated user with write access to their own board can call /cards/update, /lists/update, or /swimlanes/update to move cards, lists, or swimlanes into a private board they are not a member of. This issue is fixed in version 9.37.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wekanto a version that resolves this vulnerability.Fixed in 9.37
Event History
Frequently Asked Questions
What is the severity of CVE-2026-55234?
The severity of CVE-2026-55234 is rated as high with a score of 8.5.
How do I fix CVE-2026-55234?
To fix CVE-2026-55234, upgrade to Wekan version 9.37 or later.
What type of vulnerability is CVE-2026-55234?
CVE-2026-55234 is a broken access control vulnerability that allows authenticated users to move cards, lists, and swimlanes to unauthorized private boards.
What impact does CVE-2026-55234 have on Wekan?
CVE-2026-55234 allows any authenticated user to manipulate cards in boards that they do not have membership in, posing a risk to data integrity.
What software is affected by CVE-2026-55234?
The vulnerability CVE-2026-55234 affects Wekan versions prior to 9.37.