← Back
GHSA-qwww-vcr4-c8h2
Cross-Site Request Forgery (CSRF) in react-router (GHSA-qwww-vcr4-c8h2)
Summary
vulnerability in react-router (GHSA-qwww-vcr4-c8h2). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `8.3.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-qwww-vcr4-c8h2** has been found in react-router.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade react-router to **8.3.0** or later.
If unsure, ask your IT team or search "react-router GHSA-qwww-vcr4-c8h2" on the vendor's site.
GHSA-qwww-vcr4-c8h2 (react-router) — CWE-352 /
Patched: `8.3.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.
❓ What is the problem
**CSRF** (CWE-352) exists in react-router.
📍 Affected scope
react-router — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8.3.0**.
🛡️ 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 'react-router' .` 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 'react-router' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `react-router` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade react-router to 8.3.0ステージング環境で 8.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
react-router
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.3.0"}]}]
References
- web https://github.com/remix-run/react-router/security/advisories/GHSA-qwww-vcr4-c8h2
- web https://github.com/remix-run/react-router/commit/7a71c728ad116bd78699a258b2014ce9585729f5
- web https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v830
- web https://github.com/remix-run/react-router/releases/tag/[email protected]
- web http://github.com/remix-run/react-router/pull/15311
- web https://github.com/advisories/GHSA-qwww-vcr4-c8h2
- web https://github.com/remix-run/react-router/pull/15353
- web https://github.com/remix-run/react-router/commit/8ebd5df9932854547963e3255c8454e62430e05d
- web https://github.com/remix-run/react-router/blob/v7/CHANGELOG.md#v7182
- web https://github.com/remix-run/react-router/releases/tag/react-router%407.18.2