Vulnerability in Plane (CVE-2026-104968)
Summary
Vulnerability in Plane (CVE-2026-104968). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/workspaces/{slug}/entity-search/. Mitigation: upgrade to 1.4.0 or later.
Original description
The description as published by the source.
Plane is an open-source project management tool. Prior to 1.4.0, GET /api/workspaces/{slug}/entity-search/?query_type=user_mention returns workspace-member display names, UUIDs, and avatar URLs to any authenticated user who knows the workspace slug, even when the caller is not a workspace member. The endpoint also exposes ProjectMember rows under the same condition. SearchEndpoint in apps/api/plane/app/views/search/base.py inherits BaseAPIView with only permission_classes = [IsAuthenticated] and performs no workspace-membership check. This issue is fixed in 1.4.0.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104968 has been found in Plane.
Attackers can target a specific entry point like GET /api/workspaces/{slug}/entity-search/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Plane to 1.4.0 or later.
If unsure, ask your IT team or search "Plane CVE-2026-104968" on the vendor's site.
CVE-2026-104968 (Plane) — CWE-862
Attack surface: GET /api/workspaces/{slug}/entity-search/
Patched: 1.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Plane. Attackers reach the vulnerable code path via GET /api/workspaces/{slug}/entity-search/.
Check the vendor advisory for the affected versions of Plane. Attack surface: GET /api/workspaces/{slug}/entity-search/.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/workspaces/{slug}/entity-search/ requests with malformed payloads or SQL meta-characters. Run grep -r 'Plane' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Plane' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Planeを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/workspaces/{slug}/entity-search/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/workspaces/{slug}/entity-search/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Plane to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/workspaces/{slug}/entity-search/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。