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

ListLockBulkBleed

CVEIconVulnerability nameDate Responsible Security Disclosure byStarsProcessVulnerabilities
CVE requested

ListLockBulkBleed 2026-11-18 immanuwell Gold starGold starGold starGold star

Coordinated disclosure via GitHub Security Advisory GHSA-83w9-74mx-7v83, with the affected lines and a proof of concept against the official v13.15 image; validated and fixed by xet7.

When a board admin refused a role write access in one list (roleExceptions, #4527), a normal member could still delete and relabel that list's cards through the REST bulk routes, archive them, and copy or link new cards into the list through Meteor methods: those paths asked only for write access to the board.

Details

A board admin can give a list its own rule for a role (list.roleExceptions, #4527): for example, Normal members may read a list but not write in it. The card screen, the per-card REST routes (ListLockBleed) and the attachment API (ListLockAttachBleed) apply that rule, and client collection writes meet it in the Cards allow/deny rules. Five paths did not. DELETE /api/boards/:boardId/cards/bulk and POST /api/boards/:boardId/cards/labels take their cards from the request body, so no URL names a list, and they asked only for write access to the board. The Meteor methods archiveSelectedCards, copyCard and createLinkedCard write from server code, where allow/deny rules do not run, and asked the board and the assigned-only rule but never the list. So a normal member the list refused, with an API token or a session, could permanently delete every card in that list in one request, relabel them, archive them, and put copies or linked cards into it. Nothing outside the board was reached, and the member already had write access to the rest of the board.

Fix: the bulk routes read every card first and ask the list of each (assertCardListsNotRefused in server/lib/listPermissionGate.js) before the first write, answering 403 and changing nothing when any list refuses; each removal and relabel is then keyed on the list that was checked, so a card moved into a refusing list in between is not touched. The three methods ask assertListsWritable for every card's list, or for the destination list, before writing, and answer not-authorized. As for the other REST card routes, only a list's refusal counts: a list's grant does not open them to a role the board does not let write. The board admin, whom no list exception binds, is unaffected.

The same shape elsewhere: a search of every server path that writes a card on board-level rights alone found twelve more, fixed with the same check before their first write: converting a card to a board, adding a subtask to its landing list, createCardWithDueDate (which also did not check that the list was on the board), the iCalendar import over DDP and REST, sending and receiving board email (a reply on a card, and a new card in the Inbox or placement list), creating a version-control issue, moving cards, checklists and items between boards, History's undo, redo and Restore and the position history's undo and redo of a card, renaming an attachment, the scoped import into a list or below a card, and pressing a card's rule button. Dependency lines keep their own board-wide rule, as decided for ListLockBleed.

Detection

A refused bulk request is recorded in Admin Panel / Problems as ListLockBulkBleed (key authz.list-locked-bulk), with the route as its source. No screen calls those routes, so only a direct API call reaches the refusal. Medium severity in Problems: it never disables the account. The methods' refusals are not recorded: Copy Card's destination picker and Multi-Selection reach them in ordinary use, so a refusal there is not evidence of an attempt.

Verification

tests/listLockBulkBleed.test.cjs runs the guard itself on the reporter's board, a normal member and a list refusing normal.write, for the bulk routes and the methods. It checks the negative cases (an open list, a granting list, the board admin, a list on another board) and the record in Problems. It pins that each of the five paths, and each of the twelve siblings, asks before its first write, and scans every REST card route whose URL names no list and no card, so a new bulk route cannot skip the list. The tests for the reported paths fail on the unfixed code. tests/playwright/specs/list-lock-bulk.e2e.js replays the report against a running server: in a locked list the bulk delete, bulk labels, archive, copy and link are refused and change nothing; in an open list the same member writes, and the board admin deletes in the locked one.