criticalCVE-2024-58353

CVE-2024-58353 cal.diy vulnerability

Cal.com (repository calcom/cal.diy) in versions <= 4.7.15 is vulnerable to cross-site scripting (XSS) on the publicly accessible single booking view (e.g., /booking/<id>). Booking question (form field) labels are rendered via React's dangerouslySetInnerHTML without proper input sanitization or CSP, so an attacker who can create an event type with a malicious booking question label can inject arbitrary HTML/JavaScript that executes when a victim visits the booking view URL. Self-hosted instances with open registration are particularly at risk. The issue is fixed in version 4.7.16.

Browse Cross-site Scripting security risks
Productcal.diy
CVSS9.3
EPSSNot scored yet
UpdatedJuly 24, 2026

Quick answer

calcom cal.diy should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • <= 4.7.15

Fixed versions

  • Apply the latest vendor-supported patched version.

How to fix it

CVE-2024-58353 affects cal.diy and involves cross-site scripting. Successful exploitation may run attacker-controlled script in a trusted user's browser and expose session or application data. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. No confirmed fixed version is recorded for CVE-2024-58353; follow the linked vendor advisory, apply its mitigation, and update cal.diy as soon as a supported patched release is available.

  1. Inventory every deployment, device, package, plugin, container, build, and environment that uses cal.diy.
  2. Compare the installed version with the recorded affected range: <= 4.7.15.
  3. No confirmed fixed version is recorded for CVE-2024-58353; follow the linked vendor advisory, apply its mitigation, and update cal.diy as soon as a supported patched release is available.
  4. Until patched, reduce public exposure, disable the affected workflow where practical, and allow access only from trusted users and systems.
  5. Review configuration, roles, tokens, network paths, and exposed endpoints connected to cal.diy; remove access that is not required.
  6. Review submissions, stored content, administrator activity, CSP reports, and web logs for script payloads or suspicious browser requests.
  7. If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2024-58353 in place.
  • Use a safe regression test to confirm the affected cross-site scripting path no longer produces the vulnerable behavior.
  • Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
  • Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
  • Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

Related security risks

More published guidance from the same primary category.

Trusted references

FAQ

What is affected by CVE-2024-58353?

calcom cal.diy versions listed as affected should be reviewed: <= 4.7.15.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.