# CVE-2026-53445: Wekan: Authorization bypass in copyBoard DDP method allows any user to copy private boards

> An authenticated user can copy private boards and their contents without authorization due to missing access checks in the copyBoard method.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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-7w2h-g83c-jqrp

## What is CVE-2026-53445?

CVE-2026-53445 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.32, the Wekan copyBoard Meteor DDP method in server/publications/boards.js copies a board by caller-supplied board ID without checking this.userId, membership, or admin access. Any authenticated user can copy a private board they are not a member of, including its cards, checklists, custom fields, labels, and rules, while the REST POST /api/boards/:boardId/copy path correctly checks board admin access. This issue is fixed in version 9.32.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-53445 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53445 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-53445 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-53445/ (Markdown: https://insights.sbomify.com/CVE-2026-53445/index.md)
```

## Sources

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

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