Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104968 Overview
CVE-2026-104968 is a missing authorization vulnerability [CWE-862] in Plane, an open-source project management tool. Versions prior to 1.4.0 expose workspace member information to any authenticated user who knows a workspace slug. The GET /api/workspaces/{slug}/entity-search/?query_type=user_mention endpoint returns workspace-member display names, UUIDs, and avatar URLs without verifying that the caller belongs to the target workspace. The same endpoint also leaks ProjectMember rows under identical conditions. The root cause lies in SearchEndpoint within apps/api/plane/app/views/search/base.py, which inherits BaseAPIView with only permission_classes = [IsAuthenticated] and performs no workspace-membership check.
Critical Impact
Any authenticated Plane user can enumerate workspace members and project members of unrelated workspaces by supplying the workspace slug, exposing identity data useful for targeted phishing and reconnaissance.
Affected Products
- Plane (makeplane/plane) versions prior to 1.4.0
- SearchEndpoint in apps/api/plane/app/views/search/base.py
- Deployments exposing /api/workspaces/{slug}/entity-search/ to multi-tenant users
Discovery Timeline
- 2026-10-05 - CVE CVE-2026-104968 published to NVD
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-104968
Vulnerability Analysis
The vulnerability is a broken access control issue in Plane's entity-search API. The SearchEndpoint class handles requests scoped to a workspace slug but does not confirm the authenticated caller is a member of that workspace. When a client calls the endpoint with query_type=user_mention, the handler queries workspace members and returns display names, UUIDs, and avatar URLs. The same handler also returns ProjectMember records for projects inside the target workspace. Because the slug is the only tenant boundary enforced in the URL and no server-side membership check runs, any authenticated user in the Plane instance can read member rosters of workspaces they do not belong to.
Root Cause
The root cause is a missing authorization check [CWE-862]. SearchEndpoint inherits from BaseAPIView and declares permission_classes = [IsAuthenticated]. The class omits WorkspaceUserPermission, so Django REST Framework authenticates the caller but never validates workspace membership. The slug supplied in the URL is used solely for filtering database queries, not for access control.
Attack Vector
Exploitation requires only valid credentials on the Plane instance and knowledge or guessing of a target workspace slug. An attacker issues an authenticated HTTP GET to /api/workspaces/{slug}/entity-search/?query_type=user_mention and parses the JSON response for member identifiers. Slugs are often human-readable organization names, making enumeration straightforward in multi-tenant SaaS or shared self-hosted deployments.
# Patch from upstream commit 28ae25b564351abaf8b36d4a3ba6d32f80fbf075
# apps/api/plane/app/views/search/base.py
# Module imports
from plane.app.views.base import BaseAPIView
+from plane.app.permissions import WorkspaceUserPermission
from plane.db.models import (
Workspace,
Project,
# Source: https://github.com/makeplane/plane/commit/28ae25b564351abaf8b36d4a3ba6d32f80fbf075
The fix imports WorkspaceUserPermission and applies it to SearchEndpoint so that only members of the target workspace receive results.
Detection Methods for CVE-2026-104968
Indicators of Compromise
- Authenticated HTTP GET requests to /api/workspaces/{slug}/entity-search/ where the requesting user is not a member of {slug}.
- High-volume or sequential enumeration of workspace slugs from a single account or IP address.
- Anomalous access to entity-search with query_type=user_mention returning HTTP 200 for users with no prior activity in that workspace.
Detection Strategies
- Correlate API gateway or reverse-proxy logs against the workspace membership table to flag entity-search calls where the caller is not in WorkspaceMember for the requested slug.
- Alert on burst patterns of distinct {slug} values accessed by a single authenticated user over a short time window.
- Hunt historical logs for 200-status responses on entity-search prior to upgrading to version 1.4.0.
Monitoring Recommendations
- Forward Plane API access logs to a centralized logging or SIEM platform and retain them for retrospective hunting.
- Monitor outbound traffic from accounts that have recently queried member rosters for signs of follow-on phishing or credential-stuffing activity.
- Track the Plane application version in asset inventory and alert when instances remain below 1.4.0.
How to Mitigate CVE-2026-104968
Immediate Actions Required
- Upgrade Plane to version 1.4.0 or later, which enforces WorkspaceUserPermission on SearchEndpoint.
- Audit application logs for prior access to /api/workspaces/{slug}/entity-search/ by non-members and notify affected workspace owners.
- Rotate or review invitation workflows if workspace slugs are considered sensitive and were potentially enumerated.
Patch Information
The fix is published in Plane 1.4.0 via commit 28ae25b564351abaf8b36d4a3ba6d32f80fbf075 and pull request #9296. The patch adds WorkspaceUserPermission to SearchEndpoint so that only authenticated users who are members of the target workspace receive results. See the GitHub Security Advisory GHSA-32q3-mqpc-3mhv, the upstream commit, Pull Request #9296, and the Plane 1.4.0 release notes.
Workarounds
- Restrict access to the Plane API at the reverse proxy, allowing only authenticated sessions originating from trusted networks until the patch is applied.
- Block or rate-limit requests to /api/workspaces/*/entity-search/ at the gateway and require manual review for enumeration patterns.
- Treat workspace slugs as sensitive and rotate publicly disclosed slugs where feasible to reduce guessability.
# Example NGINX rule to rate-limit the vulnerable endpoint until upgrade
limit_req_zone $binary_remote_addr zone=plane_search:10m rate=5r/m;
location ~ ^/api/workspaces/[^/]+/entity-search/ {
limit_req zone=plane_search burst=5 nodelay;
proxy_pass http://plane_api_upstream;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

