Vulnerability in CordysCRM (CVE-2026-63647)
Summary
Vulnerability in CordysCRM (CVE-2026-63647). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.2 or later.
Original description
The description as published by the source.
CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. Prior to 1.7.2, SseController exposes the anonymous /sse/subscribe, /sse/broadcast, and /sse/close endpoints because ShiroFilter.addPublicPathFilters permits the SSE paths, and the endpoints trust the caller-controlled userId instead of deriving an identity from an authenticated principal. An unauthenticated caller can use /sse/subscribe to read another user's workflow events, approval requests, mentions, and alerts, use /sse/broadcast to inject SYSTEM_HEARTBEAT messages into another user's stream, or use /sse/close to terminate another user's channel. This vulnerability is fixed in 1.7.2.
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-63647 has been found in CordysCRM.
Risk of unauthorized operations or information disclosure.
What to do: upgrade CordysCRM to 1.7.2 or later.
If unsure, ask your IT team or search "CordysCRM CVE-2026-63647" on the vendor's site.
CVE-2026-63647 (CordysCRM) — CWE-306
Patched: 1.7.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.
A vulnerability (CWE-306) exists in CordysCRM.
Check the vendor advisory for the affected versions of CordysCRM.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.7.2.
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 'CordysCRM' . 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 'CordysCRM' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CordysCRMを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade CordysCRM to 1.7.2ステージング環境で 1.7.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。