dbcve.org
CWE-80Weakness · CWE-80

CVE-2024-58355

HIGH · 8.9 CVSS v3.1 Published 2026-07-23
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Patch available 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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/<id>) 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cal.com versions through 4.7.15 have a stored XSS vulnerability in the single booking view where booking-question field labels are rendered using React's dangerouslySetInnerHTML without sanitizing user input. An attacker who can create an event type with a malicious booking-question label can inject arbitrary JavaScript that executes when victims view the booking URL.

MitigationUpgrade to Cal.com v4.7.16 or later, which includes proper input sanitization before rendering booking-question labels via dangerouslySetInnerHTML.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Cal.com installed version
    Locate the Cal.com version file (package.json, VERSION file, or admin dashboard 'About' page) and note the version number
    Affected if Version is 4.7.15 or earlier (any version through 4.7.15)
  2. Identify active event types with booking questions
    Access the Cal.com admin or user dashboard, navigate to Event Types, and list all event types that have booking questions (custom inputs) enabled
    Affected if Any event type has booking questions configured
  3. Inspect booking question field labels
    Examine each event type's booking questions (custom inputs) and review the field labels for any suspicious HTML tags, script elements, or encoded payloads (e.g., <script>, onload=, onerror=, javascript:). Use the database directly if admin access is unavailable: SELECT * FROM booking_questions or SELECT * FROM event_type_custom_inputs
    Affected if Any booking question label contains unsanitized HTML/JavaScript such as <script>, event handlers (onclick, onerror, onload), or javascript: URIs
  4. Test booking page for XSS execution
    Create a test booking using an event type with booking questions; when submitting the booking form, inject a harmless test payload like <img src=x onerror=alert(1)> into a question label, then open the resulting booking URL to see if the script executes
    Affected if The injected payload executes as JavaScript when viewing the booking page

You are affected if Cal.com version is 4.7.15 or earlier AND booking questions are configured with field labels containing unsanitized HTML or JavaScript that could execute when the booking page is viewed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Cal.com v4.7.16 or later, which includes proper input sanitization before rendering booking-question labels via dangerouslySetInnerHTML.

Recommended fix High confidence

v4.7.16

  1. Backup your current Cal.com installation and database before upgrading
  2. Update to Cal.com v4.7.16 by pulling the latest image or cloning the updated repository
  3. Run any database migrations that are part of the v4.7.16 release
  4. Restart the Cal.com application services to apply the update
  5. Verify the upgrade was successful by logging in and checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-58355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-58355 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data