← Back
CVE-2026-63123
medium
CVSS 6.5
Cross-Site Request Forgery (CSRF) in @tinacms/cli (CVE-2026-63123)
Summary
vulnerability in @tinacms/cli (CVE-2026-63123). Data can be tampered with by attackers. Exploitable via ``false``. Mitigation: upgrade to `2.5.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-63123** has been found in @tinacms/cli.
Attackers can target a specific entry point like ``false`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @tinacms/cli to **2.5.2** or later.
If unsure, ask your IT team or search "@tinacms/cli CVE-2026-63123" on the vendor's site.
CVE-2026-63123 (@tinacms/cli) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `false` / `poc.txt`
Patched: `2.5.2` — 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.
❓ What is the problem
**CSRF** (CWE-352) exists in @tinacms/cli. Attackers reach the vulnerable code path via ``false`` without authentication.
📍 Affected scope
@tinacms/cli — . Attack surface: `false` / `poc.txt`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.5.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@tinacms/cli' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@tinacms/cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@tinacms/cli` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @tinacms/cli to 2.5.2ステージング環境で 2.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@tinacms/cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.5.2"}]}]