/

CVE-2026-68561

Severity:

HIGH RISK

(8.8)

Broken Access Control (CWE-863) in Wekan Board Updates

CVE-2026-68561

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-269, CWE-863

Impact:

Privilege Escalation and Board Takeover

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A broken access-control vulnerability in Wekan allows an authorized board member to submit a crafted board update that changes administrative and privacy-related settings.

Under affected authorization and update-handling conditions, a lower-privileged member may gain board control, expose a private board, and remove the legitimate administrator.

Affected context

The issue occurs in Wekan board update authorization when Meteor combines multiple Boards.allow({ update }) rules using OR semantics and then applies the complete update modifier. Deployments may be exposed when members with limited board permissions can reach the board update endpoint and submit changes affecting sorting, membership, permissions, or titles.

Exploit preconditions

  • Attack surface: Wekan board update operations
  • Required access: An authenticated account with membership or limited participation in the target board
  • Trigger point: A Boards.update request containing a permitted-looking sort change alongside additional field modifications
  • Why exploitation is possible: One authorization rule may approve the operation based on the presence of the sort field, while the complete modifier also changes membership, permissions, privacy, or ownership-related data

Why this happens

The underlying bug combines overly broad authorization with incomplete validation of update modifiers. A rule intended to authorize sorting changes treated the presence of sort as sufficient permission, without ensuring that sorting was the only modified field. Because Meteor combines allow rules with OR semantics, another rule could authorize the whole update, while the last-administrator safeguard examined only certain removal operations and did not cover wholesale member-array replacement.

This maps primarily to CWE-863: Incorrect Authorization, with a related CWE-269: Improper Privilege Management concern. The insecure pattern is validating one field or operation while allowing a broader modifier to alter security-sensitive state.

Potential impact

  • An authorized lower-privileged member may gain administrative control of a board
  • A private board could be made visible to additional users
  • The legitimate board administrator could be removed
  • Board membership, permissions, and content metadata could be altered
  • Organizational workflows and project data could be disrupted

General mitigation guidance

Mitigation generally focuses on enforcing authorization against the complete requested state change rather than an individual field.

Common defensive patterns include:

  • Require the update to contain only fields that the caller is authorized to modify
  • Separate sorting updates from membership, permission, privacy, and ownership changes
  • Use deny-by-default authorization for security-sensitive board fields
  • Validate both additive and replacement-style membership changes
  • Prevent updates that would leave a board without an eligible active administrator
  • Apply authorization checks after normalizing the full modifier
  • Run application services with least privilege and protect administrative operations with stronger controls

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review rules that flag authorization based on a single field while accepting a complete update modifier
  • Review of Meteor allow and deny rules for OR-combination behavior
  • Tests covering mixed-field updates, array replacement, administrator removal, and privacy changes
  • Monitoring for board updates that combine sorting changes with membership or permission changes
  • Policy enforcement requiring explicit authorization for security-sensitive fields

Automated security review tools may help identify broad update paths, missing field allowlists, and inconsistent last-administrator checks.

Sources

SourceLink
github.comgithub.com/wekan/wekan/commit/dc135f6e7d59f9f56065cd5df83b1f123ea120bb
github.comgithub.com/wekan/wekan/releases/tag/v9.89
github.comgithub.com/wekan/wekan/security/advisories/GHSA-xm8x-c8wg-jhmf

Frequently asked

questions

Yes, where the Wekan instance is reachable and an attacker has authenticated access to a board with sufficient membership privileges to submit updates.

Typically no. The described attack requires an account that can participate in the target board and reach the board update operation.

Authorize the complete update modifier, enforce explicit field allowlists, and handle membership and administrator invariants separately from ordinary sorting changes.

Use deny-by-default authorization, test mixed-field and replacement-style updates, review framework-specific allow-rule semantics, and monitor sensitive membership and permission changes.

Find out what's already
exploitable in your codebase.