CVE-2024-29891

ZITADEL Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass

HIGH
8.7
CVSS Score
Published: March 27, 2024 at 07:18 PM UTC
Updated: June 17, 2026 at 07:23 AM UTC
1 product affected across 1 vendorZitadel

Using zitadel by zitadel?

Get instant alerts when new vulnerabilities affect zitadel - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.7
Exploit prediction
EPSS 0.8%
SSVC
No known exploit

Description

ZITADEL users can upload their own avatar image and various image types are allowed. Due to a missing check, an attacker could upload HTML and pretend it is an image to gain access to the victim's account in certain scenarios. A possible victim would need to directly open the supposed image in the browser, where a session in ZITADEL needs to be active for this exploit to work. The exploit could only be reproduced if the victim was using Firefox. Chrome, Safari as well as Edge did not execute the code. This vulnerability is fixed in 2.48.3, 2.47.8, 2.46.5, 2.45.5, 2.44.7, 2.43.11, and 2.42.17.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.42.17v < 2.43.11v < 2.44.7v < 2.45.5v < 2.46.5v < 2.47.8v < 2.48.32.43.0 ≤ v < 2.43.112.44.0 ≤ v < 2.44.72.45.0 ≤ v < 2.45.52.46.0 ≤ v < 2.46.52.47.0 ≤ v < 2.47.82.48.0 ≤ v < 2.48.3
Affected range stops below 2.42.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.43.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.44.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.45.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.46.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.47.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.48.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.7HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-434CWE-79

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card