Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a cross-site scripting vulnerability within the Cal.com booking system, specifically affecting how booking questions are displayed on publicly accessible single booking pages. Maliciously crafted question labels could allow an attacker to inject harmful code, potentially executing arbitrary scripts when a victim accesses the booking link. This poses a risk to self-hosted instances with open registration.
- Attackers can inject code through booking questions.
- Matters because it impacts public booking pages.
- Confirm relevance and exposure of booking pages.
Attack Path
How an attacker could exploit the issue
An attacker could start by creating an event type with a specially crafted booking question label. This malicious label would then be displayed on the publicly accessible single booking view when a victim visits the booking URL. The vulnerability lies in how the booking question is rendered, allowing injected code to execute within the victim's browser.
- Requires authenticated access to create an event type.
- Victim visits a booking URL.
- Arbitrary code execution in victim's browser.
Live Threat
Current exploitation, exposure, and threat context
This vulnerability could allow an attacker to inject malicious HTML or JavaScript into booking question labels on publicly accessible booking pages. When a user visits a booking page with a specially crafted label, the injected code could execute in their browser, potentially leading to session hijacking or the exposure of sensitive information. This risk is higher on self-hosted instances that allow open registration.
- User booking data could be exposed.
- Malicious script executes via booking links.
- Session data may be compromised.
Operational Fix
Recommended remediation, mitigation, and detection steps
For self-hosted Cal.com instances, the application owner or platform team is primarily responsible for addressing this cross-site scripting vulnerability. The initial step involves identifying all deployed instances, confirming their internet reachability and business criticality. Once identified, the accountable owner must be located to plan remediation, which may involve vendor coordination if the instance is managed by a third party.
- Application owners should prioritize remediation.
- Verify internet-facing instances and business impact.
- Plan updates with vendor or internal teams.