ZITADEL Users Can Self-Verify Email/Phone via UpdateHumanUser 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 4.11.0, 3.4.7, 4.11.1, 1.80.0-v2.20.0.20260225053417-0261536243e5
- 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: yes
- Technical impact: partial
Summary
ZITADEL is an open source identity management platform. Prior to versions 4.11.1 and 3.4.7, a vulnerability in Zitadel's self-management capability allowed users to mark their email and phone as verified without going through an actual verification process. The patch in versions 4.11.1 and 3.4.7 resolves the issue by requiring the correct permission in case the verification flag is provided and only allows self-management of the email address and/or phone number itself. If an upgrade is not possible, an action (v2) could be used to prevent setting the verification flag on the own user.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- zitadel zitadel
From 4.0.0 · fixed in 4.11.0; fixed in 3.4.7
- github.com/zitadel/zitadelGo
From 4.0.0 · fixed in 4.11.1
- github.com/zitadel/zitadelGo
From 2.43.0 · fixed in 3.4.7
- github.com/zitadel/zitadelGo
fixed in 1.80.0-v2.20.0.20260225053417-0261536243e5