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

UnassignedAttachBleed

CVEIconVulnerability nameDate Responsible Security Disclosure byStarsProcessVulnerabilities
CVE requested

UnassignedAttachBleed 2026-11-01 Javier García Herrera Gold starGold starGold starGold starGold star

Reported privately by Javier García Herrera through GitHub Security Advisory GHSA-w26g-rc43-q6cm, with reproduction steps against the official v12.74 Docker image and a suggested fix; validated and fixed by xet7.

A member with the Normal, assigned only role whose card assignment was removed could still add a file to that card and soft-delete its existing attachment through the REST attachment API, which asked only for write access to the board. Copy and move onto a card, and the same API over DDP, had the same gap.

Details

A board member with an assigned-only role (Normal, assigned only, and the read and comment variants) sees and changes only the cards assigned to them. While assigned, such a member learns the card's id and its attachments' ids. After the board owner removed the assignment, GET /api/attachment/info/:attachmentId answered 403, but POST /api/attachment/upload still added a new file to the card and DELETE /api/attachment/delete/:attachmentId still soft-deleted its existing file: both handlers asked only whether the caller may write to the board. The raw upload stored the file through addAttachmentFromStream, which does not run the upload hook that checks the card. The DDP methods api.attachment.upload and api.attachment.delete, and copy and move onto a target card over REST and DDP, had the same gap. No file was disclosed, nothing was deleted permanently, and no other board was reachable.

Fix: every attachment API write - upload, delete, and the target card of copy and move, over REST and DDP - also asks mayWriteCardAttachment, the card rule the ordinary card Delete already applied: an assigned-only member writes only on a card assigned to them.

Detection

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

Verification

tests/unassignedAttachBleed.test.cjs drives the decision through the reported sequence - assigned, then unassigned - and scans both attachment API files: every handler that writes a card attachment after board write access must also ask the card. tests/playwright/specs/unassigned-attach-bleed.e2e.js replays the reporter's REST requests and the DDP delete against a running server.

Source fix and regression coverage