Summary
WeKan versions before 8.35 contain missing authorization checks on Integration REST API endpoints, allowing regular board members to invoke actions intended for administrators.
Under these conditions, authenticated users can enumerate, create, modify, or delete integrations and manage integration activities without holding the appropriate privileges.
Affected context
This vulnerability affects WeKan deployments that expose the Integration REST API and rely on role-based permissions to separate regular board member capabilities from administrative integration management.
It manifests specifically in JsonRoutes-based REST handlers backing integration endpoints, where permission checks are incomplete or missing.
Any environment where board members have authenticated access but should not manage integrations can be impacted, including multi-tenant or shared boards.
Exploit preconditions
- Attack surface: Integration-related REST API endpoints exposed by the WeKan server.
- Required access: Authenticated WeKan account with membership on at least one board; no special admin role is required.
- Trigger point: Direct invocation of Integration REST endpoints (e.g., via REST clients, browser dev tools, or custom scripts) to enumerate, create, update, or delete integration resources.
- Why exploitation is possible: The JsonRoutes handlers for integration operations do not consistently enforce authorization checks that distinguish administrators from normal board members, allowing any authenticated board member to perform actions reserved for privileged roles.
Why this happens
The issue stems from incomplete enforcement of authorization logic on server-side REST handlers, mapping directly to CWE-862: Missing Authorization.
While authentication correctly identifies users as board members, the integration endpoints fail to verify whether the caller has the specific privilege required to view or manage integrations.
As a result, business logic that should be conditioned on administrative roles is exposed to accounts with lower privileges, breaking the intended access control model.
Potential impact
- Board members may enumerate all integrations for a board, including sensitive webhook URLs and configuration details.
- Attackers could create new integrations that exfiltrate data or send events to attacker-controlled endpoints.
- Existing integrations may be modified or disabled, disrupting automation and notifications.
- Integration activities can be manipulated to facilitate data leakage, audit trail gaps, or misrouting of operational events.
- In some deployments, unauthorized integration control could serve as a stepping stone to broader compromise of connected systems.
General mitigation guidance
Useful mitigations focus on enforcing robust, centralized authorization around integration management and reducing exposure of sensitive integration data:
- Introduce explicit permission checks for each integration-related operation, binding them to clearly defined administrative or owner roles.
- Consolidate authorization logic into reusable helpers or middleware, ensuring all JsonRoutes handlers use the same policy rather than ad-hoc checks.
- Apply the principle of least privilege to role definitions so that only a minimal set of accounts can view or alter integration configurations and secrets.
- Avoid returning sensitive details such as webhook URLs, tokens, or headers unless strictly necessary and only to authorized roles.
- Consider logging and monitoring all integration management actions to help detect misuse and refine permissions over time.
How teams detect issues like this
Detection typically relies on reviewing access control logic and monitoring runtime behavior:
- Perform targeted code reviews on JsonRoutes-based REST handlers to confirm that each integration endpoint invokes a centralized authorization check tied to the intended role.
- Use static analysis or custom linters to flag routes that read or modify integration data without calling approved authorization helpers.
- Inspect audit logs for patterns where non-admin board members are creating or modifying integrations, especially when such activity deviates from normal usage.
- In CI/CD, define security gates or automated tests that simulate calls from lower-privileged roles to sensitive endpoints, ensuring unauthorized requests are denied.

