# CVE-2024-41953: Zitadel improperly sanitizes HTML in emails and Console UI > Attackers can inject malicious HTML into emails and UI via unsanitized usernames, potentially bypassing security controls despite CSP mitigations. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 31 Jul 2024 - **Updated:** 1 Aug 2024 - **Also known as:** GHSA-v333-7h2p-5fhv, GO-2024-3015 ## What is CVE-2024-41953? CVE-2024-41953 is a medium-severity cross-site scripting vulnerability in zitadel, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Zitadel is an open source identity management system. 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. On the user's detail page, the username was also 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. This vulnerability is fixed in 2.58.1, 2.57.1, 2.56.2, 2.55.5, 2.54.8 2.53.9, and 2.52.3. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-41953? 19 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/zitadel/zitadel` | Go | All versions | None | | `github.com/zitadel/zitadel` | Go | All versions | 0.0.0-20240731122110-189505c80fa6 | | `github.com/zitadel/zitadel` | Go | All versions | 0.0.0-20240731122110-189505c80fa6 | | `github.com/zitadel/zitadel` | Go | From 0.0.0 | 1.80.0-v2.20.0.20240731122110-189505c80fa6 | | `github.com/zitadel/zitadel` | Go | From 0.0.0 | 1.80.0-v2.20.0.20240731122110-189505c80fa6 | | `github.com/zitadel/zitadel` | Go | From 1.80.1 | 2.52.3 | | `github.com/zitadel/zitadel` | Go | From 1.80.1 | 2.52.3 | | `github.com/zitadel/zitadel` | Go | From 2.53.0 | 2.53.9 | | `github.com/zitadel/zitadel` | Go | From 2.53.0 | 2.53.9 | | `github.com/zitadel/zitadel` | Go | From 2.54.0 | 2.54.8 | | `github.com/zitadel/zitadel` | Go | From 2.54.0 | 2.54.8 | | `github.com/zitadel/zitadel` | Go | From 2.55.0 | 2.55.5 | | `github.com/zitadel/zitadel` | Go | From 2.55.0 | 2.55.5 | | `github.com/zitadel/zitadel` | Go | From 2.56.0 | 2.56.2 | | `github.com/zitadel/zitadel` | Go | From 2.56.0 | 2.56.2 | | `github.com/zitadel/zitadel` | Go | From 2.57.0 | 2.57.1 | | `github.com/zitadel/zitadel` | Go | From 2.57.0 | 2.57.1 | | `github.com/zitadel/zitadel` | Go | From 2.58.0 | 2.58.1 | | `github.com/zitadel/zitadel` | Go | From 2.58.0 | 2.58.1 | Products: Zitadel Zitadel. ## How do I fix CVE-2024-41953? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 0.0.0-20240731122110-189505c80fa6, 1.80.0-v2.20.0.20240731122110-189505c80fa6, 2.52.3 or 2.53.9. ## Is CVE-2024-41953 being exploited? There is no known exploitation of CVE-2024-41953 in the wild and no public exploit code. ## Other vulnerabilities in zitadel - [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3) - [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3) - [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0) - [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7) - [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-41953 and fix it if it is affected. What it is: CVE-2024-41953 is a medium-severity cross-site scripting vulnerability in zitadel, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-41953 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel (Go): affected all versions; no fix listed - github.com/zitadel/zitadel (Go): affected all versions; fixed in 0.0.0-20240731122110-189505c80fa6 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 0.0.0-20240731122110-189505c80fa6 - github.com/zitadel/zitadel (Go): affected from 0.0.0; fixed in 1.80.0-v2.20.0.20240731122110-189505c80fa6 - github.com/zitadel/zitadel (Go): affected from 0.0.0; fixed in 1.80.0-v2.20.0.20240731122110-189505c80fa6 - github.com/zitadel/zitadel (Go): affected from 1.80.1; fixed in 2.52.3 - github.com/zitadel/zitadel (Go): affected from 1.80.1; fixed in 2.52.3 - github.com/zitadel/zitadel (Go): affected from 2.53.0; fixed in 2.53.9 - github.com/zitadel/zitadel (Go): affected from 2.53.0; fixed in 2.53.9 - github.com/zitadel/zitadel (Go): affected from 2.54.0; fixed in 2.54.8 - github.com/zitadel/zitadel (Go): affected from 2.54.0; fixed in 2.54.8 - github.com/zitadel/zitadel (Go): affected from 2.55.0; fixed in 2.55.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-41953/ (Markdown: https://insights.sbomify.com/CVE-2024-41953/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41953 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41953 - OSV: https://osv.dev/vulnerability/CVE-2024-41953 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-41953/ Summaries are generated and may contain mistakes; the official description above is the record.