ZITADEL Users Can Self-Verify Email/Phone via API
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.4.11, 4.15.1, 1.80.0-v2.20.0.20260608144108-ed09b3df7f43
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
ZITADEL is an open source identity management platform. From 2.43.0 through 2.71.19, from 3.0.0 until 3.4.11, and from 4.0.0 until 4.15.1, the email and phone self-management API paths in internal/command/user_v2_email.go, internal/command/user_v2_phone.go, and internal/command/user_v2_human.go allowed users to request returned verification codes without the required permission, allowing users to claim ownership of email addresses or phone numbers they do not control and bypass email-based or phone-based security policies. This issue is fixed in versions 3.4.11 and 4.15.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- zitadel zitadel
From 2.43.0 · through 2.71.19; From 3.0.0-rc.1 · fixed in 3.4.11; From 4.0.0-rc.1 · fixed in 4.15.1
- github.com/zitadel/zitadelGo
All versions
- github.com/zitadel/zitadelGo
fixed in 1.80.0-v2.20.0.20260608144108-ed09b3df7f43
- github.com/zitadel/zitadelGo
From 4.0.0
- github.com/zitadel/zitadelGo
From 2.43.0