# CVE-2024-49757: Zitadel User Registration Bypass Vulnerability > Attackers can bypass disabled user registration restrictions by directly accessing the registration URL, allowing unauthorized account creation. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Oct 2024 - **Updated:** 25 Oct 2024 - **Also known as:** GHSA-3rmw-76m6-4gjc, GO-2024-3217 ## What is CVE-2024-49757? CVE-2024-49757 is a high-severity authentication bypass vulnerability in zitadel, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The open-source identity infrastructure software Zitadel allows administrators to disable the user self-registration. Due to a missing security check in versions prior to 2.64.0, 2.63.5, 2.62.7, 2.61.4, 2.60.4, 2.59.5, and 2.58.7, disabling the "User Registration allowed" option only hid the registration button on the login page. Users could bypass this restriction by directly accessing the registration URL (/ui/login/loginname) and register a user that way. Versions 2.64.0, 2.63.5, 2.62.7, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 contain a patch. No known workarounds are available. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2024-49757? 13 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 | 2.58.7 | | `github.com/zitadel/zitadel` | Go | All versions | 2.58.7 | | `github.com/zitadel/zitadel` | Go | From 2.59.0 | 2.59.5 | | `github.com/zitadel/zitadel` | Go | From 2.59.0 | 2.59.5 | | `github.com/zitadel/zitadel` | Go | From 2.60.0 | 2.60.4 | | `github.com/zitadel/zitadel` | Go | From 2.60.0 | 2.60.4 | | `github.com/zitadel/zitadel` | Go | From 2.61.0 | 2.61.4 | | `github.com/zitadel/zitadel` | Go | From 2.61.0 | 2.61.4 | | `github.com/zitadel/zitadel` | Go | From 2.62.0 | 2.62.7 | | `github.com/zitadel/zitadel` | Go | From 2.62.0 | 2.62.7 | | `github.com/zitadel/zitadel` | Go | From 2.63.0 | 2.63.5 | | `github.com/zitadel/zitadel` | Go | From 2.63.0 | 2.63.5 | Products: Zitadel Zitadel. ## How do I fix CVE-2024-49757? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 2.58.7, 2.59.5, 2.60.4 or 2.61.4. ## Is CVE-2024-49757 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49757 exists. Public exploit code: - Zitadel - User Registration Bypass (nuclei): http/cves/2024/CVE-2024-49757.yaml ## 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-49757 and fix it if it is affected. What it is: CVE-2024-49757 is a high-severity authentication bypass vulnerability in zitadel, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49757 exists. 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 2.58.7 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.58.7 - github.com/zitadel/zitadel (Go): affected from 2.59.0; fixed in 2.59.5 - github.com/zitadel/zitadel (Go): affected from 2.59.0; fixed in 2.59.5 - github.com/zitadel/zitadel (Go): affected from 2.60.0; fixed in 2.60.4 - github.com/zitadel/zitadel (Go): affected from 2.60.0; fixed in 2.60.4 - github.com/zitadel/zitadel (Go): affected from 2.61.0; fixed in 2.61.4 - github.com/zitadel/zitadel (Go): affected from 2.61.0; fixed in 2.61.4 - github.com/zitadel/zitadel (Go): affected from 2.62.0; fixed in 2.62.7 - github.com/zitadel/zitadel (Go): affected from 2.62.0; fixed in 2.62.7 - github.com/zitadel/zitadel (Go): affected from 2.63.0; fixed in 2.63.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-49757/ (Markdown: https://insights.sbomify.com/CVE-2024-49757/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-49757 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-49757 - OSV: https://osv.dev/vulnerability/CVE-2024-49757 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-49757/ Summaries are generated and may contain mistakes; the official description above is the record.