CVE-2024-58355

XSS

Public PoCXSS

Published

23 July 2026

Modified

30 July 2026

CVSS Score v4 9.3

Click a component to see what it means

Raw vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS Score 0.0029 21th percentile

Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2024-58355 is a critical-severity Basic XSS (CWE-80) vulnerability. Its CVSS base score is 9.3 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2024-55700

Vulnerability Data

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.

CWE(s): CWE-80

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access

Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.

attack.mitre.org →

T1539 Steal Web Session Cookie Credential Access

An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.

attack.mitre.org →

T1189 Drive-by Compromise Initial Access

Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-58054Shared CWE-80

CVE-2025-12753Shared CWE-80

CVE-2024-10592Shared CWE-80

CVE-2025-33110Shared CWE-80

CVE-2024-34507Shared CWE-80

CVE-2025-23392Shared CWE-80

CVE-2023-1013Shared CWE-80

CVE-2026-32732Shared CWE-80

CVE-2026-27166Shared CWE-80

CVE-2025-60100Shared CWE-80

Affected Assets

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V1.2.1
V1.3.1
V1.3.3
V1.3.4

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.

SI-10 Information Input Validation good match

Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly require output encoding and input validation that prevent basic XSS.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing in development catches unneutralized script tags before release.

A.8.25 Secure development life cycle partial match

prevents

Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.

A.8.26 Application security requirements partial match

prevents

Application security requirements explicitly call for neutralization of script-related HTML tags.

A.8.28 Secure coding partial match

prevents

Secure coding standards require proper escaping of <, >, & to block XSS.