# CVE-2026-55234: Missing authorization in wekan

> Authenticated users can move cards, lists, or swimlanes into private boards they do not belong to due to missing validation of the target board ID.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-gm7v-pc38-53jr

## What is CVE-2026-55234?

CVE-2026-55234 is a high-severity missing authorization vulnerability in wekan, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-55234?


## How do I fix CVE-2026-55234?

No fix has been published for CVE-2026-55234 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55234 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55234 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55234 and fix it if it is affected.

What it is: CVE-2026-55234 is a high-severity missing authorization vulnerability in wekan, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55234 exists.

Affected product: wekan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55234/ (Markdown: https://insights.sbomify.com/CVE-2026-55234/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55234
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55234
- OSV: https://osv.dev/vulnerability/CVE-2026-55234

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55234/
Summaries are generated and may contain mistakes; the official description above is the record.