Skip to main content
Vulnerability Database/CVE-2026-104963

CVE-2026-104963: Plane Project Management Information Disclosure

CVE-2026-104963 is an information disclosure vulnerability in Plane project management tool that allows workspace members to access private project data. This post covers technical details, affected versions, impact, and mitigation.

Published:

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-104963 Overview

Plane is an open-source project management tool that organizes work into projects, cycles, and modules within a workspace. CVE-2026-104963 is an information disclosure vulnerability [CWE-200] affecting Plane versions prior to 1.4.0. The WorkspaceCyclesEndpoint and WorkspaceModulesEndpoint return records for every project in a workspace without verifying whether the requester belongs to each project. Any authenticated workspace member, including a Guest with access to only one project, can enumerate data from private projects they have no membership in. The issue is fixed in version 1.4.0.

Critical Impact

Authenticated workspace members, including low-privilege Guests, can enumerate cycle and module metadata — names, descriptions, sprint dates, issue counts, progress snapshots, external integration IDs, linked URLs, and member lists — across private projects they do not belong to.

Affected Products

  • Plane versions prior to 1.4.0
  • WorkspaceCyclesEndpoint (GET /api/workspaces/{slug}/cycles/)
  • WorkspaceModulesEndpoint (GET /api/workspaces/{slug}/modules/)

Discovery Timeline

  • 2026-10-05 - CVE-2026-104963 published to NVD
  • 2026-10-07 - Last updated in NVD database

Technical Details for CVE-2026-104963

Vulnerability Analysis

The vulnerability stems from missing project-membership authorization checks on two workspace-scoped list endpoints. In vulnerable builds, WorkspaceCyclesEndpoint.get() executes Cycle.objects.filter(workspace__slug=slug) and WorkspaceModulesEndpoint.get() executes Module.objects.filter(workspace__slug=slug). Both queries scope results only by workspace, not by whether the requesting user is an active member of each project returned.

The sibling WorkspaceLabelsEndpoint and WorkspaceStatesEndpoint apply the correct project__project_projectmember__member=request.user filter. This makes the cycle and module endpoints inconsistent outliers in the authorization model. The disclosed data includes cycle and module names, descriptions, sprint dates, issue counts, progress snapshots, external integration IDs, linked URLs, and member lists.

Root Cause

The root cause is a broken access control pattern [CWE-200]. The ORM query filters on workspace scope only and omits the project-membership predicate used by comparable endpoints. Workspace Guests are intended to see only projects they are added to, but this filter gap exposes every project in the workspace.

Attack Vector

An attacker needs an authenticated session as any workspace member, including the lowest Guest role scoped to a single project. The attacker issues an HTTP GET to /api/workspaces/{slug}/cycles/ or /api/workspaces/{slug}/modules/. The response contains serialized records for cycles and modules belonging to every project in the workspace, enabling reconnaissance of private roadmaps, team composition, and integration identifiers.

python
# Security patch — apps/api/plane/app/views/workspace/cycle.py
    def get(self, request, slug):
        cycles = (
-           Cycle.objects.filter(workspace__slug=slug)
+           Cycle.objects.filter(
+               workspace__slug=slug,
+               project__project_projectmember__member=request.user,
+               project__project_projectmember__is_active=True,
+               project__archived_at__isnull=True,
+           )
            .select_related("project")
            .select_related("workspace")
            .select_related("owned_by")

Source: GitHub Commit b3591b9e

The equivalent fix is applied to apps/api/plane/app/views/workspace/module.py, adding the same project-membership predicate to the Module.objects.filter(...) query.

Detection Methods for CVE-2026-104963

Indicators of Compromise

  • HTTP GET requests to /api/workspaces/{slug}/cycles/ or /api/workspaces/{slug}/modules/ originating from accounts with Guest or limited project scope.
  • Response payload sizes on these endpoints that are disproportionately large relative to the requester's project assignments.
  • Repeated enumeration of workspace listing endpoints from a single session within a short time window.

Detection Strategies

  • Correlate API access logs against the project-membership table to flag responses that include project_id values the requester is not a member of.
  • Alert on first-time access to cycles or modules endpoints by Guest-role accounts.
  • Compare returned project_id sets between WorkspaceCyclesEndpoint and WorkspaceLabelsEndpoint for the same user; divergence indicates vulnerable behavior.

Monitoring Recommendations

  • Enable verbose API audit logging on the Plane application tier, capturing user ID, role, endpoint, and project IDs returned.
  • Monitor for anomalous read volume on workspace-scoped list endpoints, especially from newly provisioned or low-privilege accounts.
  • Track the running Plane version in CI/CD and container registries to confirm all deployments are on 1.4.0 or later.

How to Mitigate CVE-2026-104963

Immediate Actions Required

  • Upgrade Plane to version 1.4.0 or later, which applies the project-membership filter to both affected endpoints.
  • Audit workspace Guest and member accounts and remove any that are not required.
  • Review access logs for the two affected endpoints since the vulnerable version was deployed and treat exposed cycle, module, and integration metadata as disclosed.

Patch Information

The fix is included in Plane v1.4.0. Both WorkspaceCyclesEndpoint and WorkspaceModulesEndpoint now scope their querysets with project__project_projectmember__member=request.user, project__project_projectmember__is_active=True, and project__archived_at__isnull=True. See the GitHub Security Advisory GHSA-wcc5-qgfr-8g9c, Pull Request #9373, and Release v1.4.0.

Workarounds

  • If immediate upgrade is not possible, restrict network access to the Plane API so that only trusted users can reach the affected endpoints.
  • Temporarily remove Guest-role accounts or reduce the number of projects per workspace to minimize the scope of disclosure.
  • Place a reverse proxy or WAF rule in front of /api/workspaces/{slug}/cycles/ and /api/workspaces/{slug}/modules/ to block requests from untrusted sessions until the patch is applied.
bash
# Upgrade Plane to the patched release
git fetch --tags
git checkout v1.4.0
docker compose pull
docker compose up -d

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.