Hall of Fame
Back to Hall of Fame Contents Back to WeKan Website

UnassignedArchiveBleed

CVEIconVulnerability nameDate Responsible Security Disclosure byStarsProcessVulnerabilities
CVE requested

UnassignedArchiveBleed 2026-11-08 tsurutanmen Gold starGold starGold starGold starGold star

Reported privately by tsurutanmen through GitHub Security Advisory GHSA-6xqf-jh8x-4wxc, from a read-only review of the source with the affected lines and a suggested fix; validated and fixed by xet7.

A member with the Normal, assigned only role could archive any card on the board, including cards not assigned to them and cards they cannot see, with the archiveSelectedCards method, and turn any card into a linked-board card with createBoardFromCard: both asked only for write access to the board.

Details

A board member with an assigned-only role (Normal, assigned only) sees and changes only the cards assigned to them. The role has the board's write capability, and the DDP methods archiveSelectedCards(boardId, cardIds) and createBoardFromCard(cardId, title) asked for nothing more. Such a member who knew a card's id - from a link shared with them, or from before their role was changed - archived that card and its subtasks, so hiding another member's work, or turned the card into a link to a new board. The REST routes and the other card methods (copy, save as template, the collection writes) already applied the card rule; these two did not. Nothing was disclosed and nothing was deleted permanently: an archived card can be restored.

Fix: after the board check, both methods also ask assignedOnlyAllowsCard, as copyCard does: an assigned-only member changes only a card assigned to them. archiveSelectedCards checks every card of the selection before it archives the first, so a refused selection changes nothing.

Detection

A refusal is recorded in Admin Panel / Problems as UnassignedArchiveBleed (key authz.assigned-card-write). The interface never offers an assigned-only member a card that is not theirs, so only a caller using an id from elsewhere reaches the refusal. Medium severity: it never disables the account.

Verification

tests/assignedCardMethods.test.cjs drives the decision through the reported case, checks that both methods ask before their first write, and scans every server method that takes a card id: none may decide by the board's write access alone. tests/playwright/specs/assigned-card-methods.e2e.js replays the reporter's calls against a running server.

Source fix and regression coverage