| CVE | Icon | Vulnerability name | Date | Responsible Security Disclosure by | Stars | Process | Vulnerabilities |
|---|---|---|---|---|---|---|---|
| CVE requested | CreateBleed | 2026-11-07 | tsurutanmen | Reported privately by tsurutanmen through GitHub Security Advisory GHSA-qcfm-2g4w-wqcc, with the code paths, a proof of concept and a suggested fix; validated and fixed by xet7. |
With "Only admins can create boards" switched on in Admin Panel / Settings / Visibility, a user who is not an admin could still create boards: the setting was checked only by the Add Board form, not by a board insert from the browser console, the REST API, an import, a copy, a clone or a card turned into a board. |
The setting (issue #4475) was read in one place, the createBoardWithInitialSwimlanes method behind the Add Board form, and the interface hid that form for a user who is not an admin. Everywhere else a board could be made, nothing asked: Boards.insert({ title: 'x', permission: 'private' }) in the browser console reached the board collection's allow rule, which approves any signed-in user; POST /api/boards and the two board import routes checked only that the caller was signed in - the report. Reviewing the fix found the same gap in the import, clone and copy methods, POST /api/boards/:boardId/copy, and "Create board from card". The boards belonged to their creator; no other user's data was read or changed. Affected v12.99 and earlier.
Fix: one decision, models/lib/boardCreationPolicy.js, and one guard, server/lib/boardCreationGuard.js, asked by every path that creates a working board for a user before anything is written, and by a new deny rule for a client insert. A board template stays every member's own, and the boards WeKan makes by itself - a user's Templates board, a board's subtasks board - are not user creations. A refused REST call answers 403. Duplicate in the All Boards sidebar and "Create board from card" are hidden like Add Board.
A refusal is recorded in Admin Panel / Problems as CreateBleed (key authz.board-creation). The interface offers none of these paths to a user who is not an admin while the setting is on, so only a client bypassing it reaches the refusal. Low severity: it never disables the account, because a browser tab opened before the administrator switched the setting on still shows the buttons.
tests/createBleed.test.cjs runs the decision, the guard and the real deny rule against the reporter's console insert, and fails if any path that creates a board for a user does not ask the guard, or if anything else reads the setting. tests/playwright/specs/createbleed-board-creation-admin-only.e2e.js replays the report - the console insert, the REST and import calls, a copy and a card turned into a board - against a running server, and checks that an administrator and a board template still work.