Quick answers
- Is CVE-2026-104963 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104963 being exploited in the wild.
- How severe is CVE-2026-104963?
- Medium severity, with a CVSS score of 4.3, published 5 October 2026.
- Which products and versions are affected?
- Plane before 1.4.0.
- Is there a fix for CVE-2026-104963?
- Yes: fixed in 1.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104963 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104963?
- Check whether you run Plane at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.4.0
Technical details
The WorkspaceCyclesEndpoint and WorkspaceModulesEndpoint API routes filter results by workspace alone without checking project membership, allowing any authenticated workspace member to enumerate cycles and modules across all projects. The vulnerability exists because these endpoints use only WorkspaceViewerPermission (any active workspace member) and lack the project__project_projectmember__member filter that related endpoints (WorkspaceLabelsEndpoint, WorkspaceStatesEndpoint) correctly apply. An authenticated attacker with guest access to one project can retrieve metadata for cycles and modules in any private project within the same workspace.
Affected products
- Plane Plane before 1.4.0
Timeline
- 2026-10-05: disclosed
- 2026-07-16: patched