Cross-Site Request Forgery (CSRF) in HedgeDoc (CVE-2025-66629)
Summary
Vulnerability in HedgeDoc (CVE-2025-66629). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.10.4 or later.
Original description
The description as published by the source.
HedgeDoc is an open source, real-time, collaborative, markdown notes application. Prior to 1.10.4, some of HedgeDoc's OAuth2 endpoints for social login providers such as Google, GitHub, GitLab, Facebook or Dropbox lack CSRF protection, since they don't send a state parameter and verify the response using this parameter. This vulnerability is fixed in 1.10.4.
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-2025-66629 has been found in HedgeDoc.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade HedgeDoc to 1.10.4 or later.
If unsure, ask your IT team or search "HedgeDoc CVE-2025-66629" on the vendor's site.
CVE-2025-66629 (HedgeDoc) — CWE-352 / CVSS v3 3.7
Attack vector: remote (network-reachable)
Patched: 1.10.4 — 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.
CSRF (CWE-352) exists in HedgeDoc.
Check the vendor advisory for the affected versions of HedgeDoc.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 1.10.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'HedgeDoc' . 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 'HedgeDoc' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
HedgeDocを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade HedgeDoc to 1.10.4ステージング環境で 1.10.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。