Vulnerability in Plane (CVE-2026-104966)
Summary
Vulnerability in Plane (CVE-2026-104966). Risk of unauthorized operations or information disclosure. Exploitable via PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/. 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, two endpoint families fail to verify that nested resource identifiers belong to the workspace and project named in the URL. An authenticated user can read or modify estimates from another workspace through PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/, and can inject comments into an issue from another workspace through POST /api/workspaces/{slug}/projects/{project_id}/issues/{issue_id}/comments/. ProjectEntityPermission verifies membership in the workspace and project from the URL, but estimate_id and issue_id are fetched by primary key without confirming the same scope. The list, retrieve, and destroy handlers correctly scope their queries, demonstrating the inconsistency. 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-104966 has been found in Plane.
Attackers can target a specific entry point like PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/ 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-104966" on the vendor's site.
CVE-2026-104966 (Plane) — CWE-639
Attack surface: PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/ / POST /api/workspaces/{slug}/projects/{project_id}/issues/{issue_id}/comments/.
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-639) exists in Plane. Attackers reach the vulnerable code path via PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/.
Check the vendor advisory for the affected versions of Plane. Attack surface: PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/ / POST /api/workspaces/{slug}/projects/{project_id}/issues/{issue_id}/comments/..
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 PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/ 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 'PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/への異常なリクエスト (不正な認証ヘッダ・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 PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。