CVE-2026-53445
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWekan 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe copyBoard Meteor DDP method in Wekan prior to 9.32 lacks authorization checks (this.userId, membership, and admin access validation), allowing any authenticated user to copy private boards they are not members of by supplying a board ID. This exposes all board data including cards, checklists, custom fields, labels, and rules, while the REST API endpoint correctly enforces admin access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Wekan installation and versionCheck the Wekan version by inspecting the frontend footer, checking the /api/version endpoint, or examining the package.json/version file in the Wekan installation directory. Compare this version to the 9.32 threshold.Affected if The installed version is prior to 9.32 (e.g., 9.31, 9.0, 8.x, etc.)
-
Confirm Meteor DDP endpoint is accessibleVerify that the Meteor DDP interface is reachable. This is typically the same host/port as the Wekan web UI (port 443 or 80). The DDP protocol runs over WebSocket on the same HTTP port.Affected if The Wekan web interface is publicly or internally accessible without additional network segmentation.
-
Check if user authentication is enabledDetermine whether local user registration or external authentication (such as LDAP, SAML, or OAuth) is configured and allows users to obtain valid login credentials. Check the Wekan settings for authentication methods.Affected if Users can register or authenticate to obtain valid credentials, allowing them to invoke the DDP method.
-
Verify the copyBoard DDP method existsConnect to the Wekan DDP endpoint using a WebSocket client and inspect available methods. The vulnerable method is named 'copyBoard'. This method should be present in versions prior to the fix.Affected if The 'copyBoard' method is exposed via the DDP interface and responds to invocation with board ID parameters.
A user is affected if Wekan version is below 9.32, the DDP endpoint is accessible, and authentication allows users to obtain valid credentials that can be used to invoke the unprotected copyBoard method.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Wekan version 9.32 or later which implements proper authorization checks in the copyBoard method.
9.32
- 1. Backup your Wekan database and configuration before upgrading.
- 2. Check your current Wekan version (typically via the UI under Account > Settings or via the about page).
- 3. Upgrade Wekan to version 9.32 or later.
- 4. Verify the upgrade was successful by checking the version number.
- 5. Test that the copyBoard functionality now properly requires authorization (users should no longer be able to copy boards they are not members of or admins of).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53445 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data