Summary
Wekan versions prior to 8.20 expose migration functionality to non-administrative users due to insufficient permission checks.
Under certain conditions, this can allow unauthorized migration operations that modify board data or system state without proper administrative control.
Affected context
This vulnerability affects Wekan instances where application-level permissions are expected to restrict sensitive maintenance or migration operations to administrators.
The issue occurs in deployments where any authenticated or non-administrative user can reach endpoints or UI flows tied to migration features.
Because migration logic typically performs high-impact changes to data structures and configuration, exposing it beyond administrators increases the risk of unintended or malicious modifications.
Exploit preconditions
- Attack surface: Wekan web application (HTTP endpoints or actions related to migration features)
- Required access: Ability to authenticate as a non-administrative user or otherwise reach the migration interface
- Trigger point: Invoking the migration functionality (e.g., calling migration endpoints or triggering migration actions through the UI or API)
- Why exploitation is possible: The authorization layer does not correctly enforce that only administrative roles can invoke migration operations, allowing lower-privileged users to perform actions that should be restricted.
Why this happens
The underlying bug is a missing or incomplete authorization check around a sensitive operation, aligning with CWE-863: Improper Authorization.
In this pattern, the system assumes that access to a feature implies the right to perform an operation, instead of explicitly verifying that the caller has the required administrative role.
Migration routines are often implemented as internal maintenance utilities, and if they are exposed via routes or UI components without explicit role checks, non-privileged users can trigger high-impact actions.
Potential impact
- Non-administrative users could initiate data migrations that affect board structure and content.
- Unintended schema or configuration changes could degrade availability or integrity of boards.
- Unauthorized changes to system-level data organization may lead to data loss or inconsistent states.
- In multi-tenant or large deployments, a malicious user could disrupt other users' boards or workflows.
General mitigation guidance
Mitigation generally focuses on enforcing strict, explicit authorization for all sensitive operations:
- Require explicit administrative roles or equivalent high-privilege permissions for any migration-related endpoint or action.
- Centralize authorization decisions so that access control is enforced uniformly across UI and API layers.
- Apply the principle of least privilege by limiting which roles can perform system-wide or schema-altering actions.
- Introduce defense-in-depth checks at both the routing/controller level and the business-logic layer for migration routines.
- Where possible, separate maintenance interfaces from general user interfaces, and restrict them to controlled environments.
How teams detect issues like this
Effective detection often combines code-level and behavioral approaches:
- Use static analysis or code search to identify sensitive functions (e.g., migration, admin, maintenance actions) that lack explicit role checks or authorization guards.
- During code review, treat any operations that modify system configuration, schemas, or bulk data as requiring explicit privilege checks and documented access control.
- Implement security test cases that attempt to perform migration actions with different user roles to validate that authorization is enforced.
- Consider automated policy enforcement in CI/CD that flags new routes or handlers exposing migration or administrative functions without authorization middleware.

