Vulnerability in Cal.com (CVE-2024-58355)
Summary
Vulnerability in Cal.com (CVE-2024-58355). Confidential information can be exposed externally. Mitigation: upgrade to 4.7.16 or later.
Original description
The description as published by the source.
Cal.com (calcom/cal.diy) versions through 4.7.15 contain a stored cross-site scripting vulnerability. The single booking view (e.g., https://app.cal.com/booking/) renders booking-question field labels via React's dangerouslySetInnerHTML without sanitizing or escaping user input. An attacker who can create an event type with a malicious booking-question label can inject arbitrary HTML/JavaScript that executes when a victim opens the crafted booking URL. The issue is fixed in v4.7.16.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2024-58355 has been found in Cal.com.
Confidential information can be exposed externally. CVSS score: 8.9/10.
What to do: upgrade Cal.com to 4.7.16 or later.
If unsure, ask your IT team or search "Cal.com CVE-2024-58355" on the vendor's site.
CVE-2024-58355 (Cal.com) — CWE-80 / CVSS v3 8.9
Attack vector: remote (network-reachable)
Patched: 4.7.16 — 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-80) exists in Cal.com.
Check the vendor advisory for the affected versions of Cal.com.
Severity: High (CVSS 8.9/10). Confidential information can be exposed externally.
Update to 4.7.16.
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 'Cal.com' . 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 'Cal.com' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Cal.comを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Cal.com to 4.7.16ステージング環境で 4.7.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web github.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com