dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-55234

HIGH · 8.5 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

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 · unedited
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.

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 confidence

Wekan prior to 9.37 has an authorization bypass in the DDP update handlers for cards, lists, and swimlanes. The permission checks in server/permissions/cards.js, lists.js, and swimlanes.js only verify the stored source boardId but do not validate any new boardId provided in the update modifier, allowing authenticated users to move content to private boards they are not members of.

MitigationUpgrade Wekan to version 9.37 or later which includes proper validation of the target boardId in the update modifier.

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
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Wekan version
    Access the Wekan login page or API endpoint and look for version information in the footer, or check the server's package.json/changelog for the Wekan version number
    Affected if The installed version is prior to 9.37 (e.g., 9.36, 9.35, etc.)
  2. Verify DDP is accessible
    Confirm the Wekan server exposes DDP endpoints (typically at /websocket or port 1124 for Meteor DDP connections). Check if unauthenticated DDP connections can be established or if authenticated WebSocket connections work
    Affected if DDP protocol is enabled and accessible to authenticated users (default configuration)
  3. Examine permission validation files
    On the server filesystem, inspect server/permissions/cards.js, server/permissions/lists.js, and server/permissions/swimlanes.js. Look for update handler functions that accept a boardId modifier but only validate against the source boardId stored in the document
    Affected if The permission files exist and contain update handlers that do not validate new boardId values in the update modifier
  4. Test cross-board move capability
    Using an authenticated user account with access to one board, attempt to move a card/list/swimlane via DDP update to a different board ID where the user is not a member. Observe if the operation succeeds
    Affected if The update succeeds and the item is moved to the private board without permission error
  5. Verify board membership configuration
    Check the board membership data model to confirm users can be members of some boards and non-members of others, creating the condition where unauthorized moves could occur
    Affected if The user is a member of at least one board but not all boards in the system

A user is affected if they run Wekan version prior to 9.37 with DDP access enabled and can move items to boards they are not members of.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Wekan to version 9.37 or later which includes proper validation of the target boardId in the update modifier.

Recommended fix High confidence

version 9.37

  1. 1. Back up your existing Wekan database and configuration files before upgrading.
  2. 2. Upgrade Wekan to version 9.37. The exact upgrade method depends on your installation method (Docker, npm, or source). For Docker: pull the new image tag (e.g., wekan:9.37) and recreate the container.
  3. 3. After upgrading, verify that /cards/update, /lists/update, and /swimlanes/update now properly validate the new boardId in the update modifier.
  4. 4. Confirm that authenticated users can no longer move cards, lists, or swimlanes into private boards they are not a member of.
  5. 5. Test that normal board operations (creating, moving within your own boards) continue to work correctly.
Caveat Review Wekan 9.37 release notes for any other changes or deprecations that may affect your instance

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55234 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55234 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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