SSRF (Server-Side Request Forgery) in CordysCRM (CVE-2026-76900)
Summary
SSRF in CordysCRM (CVE-2026-76900). Confidential information can be exposed externally. Exploitable via POST /approval-flow/add.
Original description
The description as published by the source.
CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. In version 1.7.3, ApprovalResourceService.sendWebHook reads WebHookConfig.webHookUrl from stored approval-node configuration and passes it through ApprovalFlowService.updateApprovalPostField to HttpClientUtils without the SSRF validation used by the optional testConnect path. A user with PROCESS_SETTING_ADD can configure an internal URL through POST /approval-flow/add and cause the server to request it when POST /approval-action/approve executes the approval action, enabling cloud metadata access, internal network reconnaissance, and interaction with reachable internal services. This issue is fixed in version 1.7.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-2026-76900 has been found in CordysCRM.
Attackers can target a specific entry point like POST /approval-flow/add over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CordysCRM CVE-2026-76900" on the vendor's site.
CVE-2026-76900 (CordysCRM) — CWE-918 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /approval-flow/add / POST /approval-action/approve
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.
SSRF (CWE-918) exists in CordysCRM. Attackers reach the vulnerable code path via POST /approval-flow/add.
Check the vendor advisory for the affected versions of CordysCRM. Attack surface: POST /approval-flow/add / POST /approval-action/approve.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /approval-flow/add requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /approval-flow/add' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /approval-flow/addへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /approval-flow/add on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。