Summary
Workarounds
There is no workaround since a patch is already available.
Questions
If you have any questions or comments about this advisory, please email us at [email protected]
Credits
Thanks to Sushmita Poudel and David Underwood for reporting this.
Impact
ZITADEL uses HTML for emails and renders certain information such as usernames dynamically. That information can be entered by users or administrators. Due to a missing output sanitization, these emails could include malicious code.
This may potentially lead to a threat where an attacker, without privileges, could send out altered notifications that are part of the registration processes. An attacker could create a malicious link, where the injected code would be rendered as part of the email.
During investigation of this issue a related issue was found and mitigated, where on the user's detail page the username was not sanitized and would also render HTML, giving an attacker the same vulnerability.
While it was possible to inject HTML including javascript, the execution of such scripts would be prevented by most email clients and the Content Security Policy in Console UI.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2024-41953 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.53.9, 2.54.8, 2.55.5, 2.56.2, 2.57.1, 2.58.1, 0.0.0-20240731122110-189505c80fa6, 2.52.3, 1.80.0-v2.20.0.20240731122110-189505c80fa6); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
2.x versions are fixed on >= 2.58.1
2.57.x versions are fixed on >= 2.57.1
2.56.x versions are fixed on >= 2.56.2
2.55.x versions are fixed on >= 2.55.5
2.54.x versions are fixed on >= 2.54.8
2.53.x versions are fixed on >= 2.53.9
2.52.x versions are fixed on >= 2.52.9
Frequently Asked Questions
- What is CVE-2024-41953? CVE-2024-41953 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 2.53.0, < 2.53.9. It is fixed in 2.53.9, 2.54.8, 2.55.5, 2.56.2, 2.57.1, 2.58.1, 0.0.0-20240731122110-189505c80fa6, 2.52.3, 1.80.0-v2.20.0.20240731122110-189505c80fa6. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2024-41953? CVE-2024-41953 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/zitadel/zitadel are affected by CVE-2024-41953? github.com/zitadel/zitadel (go) versions >= 2.53.0, < 2.53.9 is affected.
- Is there a fix for CVE-2024-41953? Yes. CVE-2024-41953 is fixed in 2.53.9, 2.54.8, 2.55.5, 2.56.2, 2.57.1, 2.58.1, 0.0.0-20240731122110-189505c80fa6, 2.52.3, 1.80.0-v2.20.0.20240731122110-189505c80fa6. Upgrade to this version or later.
- Is CVE-2024-41953 exploitable, and should I be worried? Whether CVE-2024-41953 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-41953 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-41953?
- Upgrade
github.com/zitadel/zitadelto 2.53.9 or later - Upgrade
github.com/zitadel/zitadelto 2.54.8 or later - Upgrade
github.com/zitadel/zitadelto 2.55.5 or later - Upgrade
github.com/zitadel/zitadelto 2.56.2 or later - Upgrade
github.com/zitadel/zitadelto 2.57.1 or later - Upgrade
github.com/zitadel/zitadelto 2.58.1 or later - Upgrade
github.com/zitadel/zitadelto 0.0.0-20240731122110-189505c80fa6 or later - Upgrade
github.com/zitadel/zitadelto 2.52.3 or later - Upgrade
github.com/zitadel/zitadelto 1.80.0-v2.20.0.20240731122110-189505c80fa6 or later
- Upgrade