Reflected Cross-Site Scripting (XSS) in zenml
CVE-2024-5062 · GHSA-3434-hc3m-8mmm · published 2024-06-30 · updated 2025-01-21
- Severity
- Medium
- CVSS score
- 6.1
- Chance of exploitation (EPSS)
- 0.39%
- Fixed in
- 0.58.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
A reflected Cross-Site Scripting (XSS) vulnerability was identified in zenml-io/zenml version 0.57.1. The vulnerability exists due to improper neutralization of input during web page generation, specifically within the survey redirect parameter. This flaw allows an attacker to redirect users to a specified URL after completing a survey, without proper validation of the 'redirect' parameter. Consequently, an attacker can execute arbitrary JavaScript code in the context of the user's browser session. This vulnerability could be exploited to steal cookies, potentially leading to account takeover.
Upgrade zenml to 0.58.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| zenml | PyPI | = 0.57.1 | 0.58.0 |
- CriticalJupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSPjupyter-server
- CriticalMalicious website can execute commands on the local system through XSS in the OpenCode web UIopencode-ai
- CriticalFlowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panelflowise
- CriticalMLFlow Cross-site Scripting vulnerability leads to client-side Remote Code Executionmlflow
- CriticalCross-site Scripting in MLFlowmlflow
- HighPraisonAI: Prompt Injection Defense Bypassed for HIGH-Level Threatspraisonai
- CriticalDirectory traversal in zenmlzenml
- HighZenML unauthenticated DoS via Multipart Boundryzenml
- HighZenML Server Remote Privilege Escalation Vulnerabilityzenml, zenml, zenml, zenml
- MediumZenML is vulnerable to Path Traversal through its `PathMaterializer` classzenml
- MediumMissing ratelimit on passwrod resets in zenmlzenml
- MediumImproper line feed handling in zenmlzenml
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.