# CVE-2025-25296: Label Studio allows Cross-Site Scripting (XSS) via GET request to `/projects/upload-example` endpoint > Attackers can execute arbitrary JavaScript in victims' browsers via a crafted URL, potentially stealing data or hijacking sessions. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Feb 2025 - **Updated:** 14 Feb 2025 - **Also known as:** GHSA-wpq5-3366-mqw4, PYSEC-2026-1504 ## What is CVE-2025-25296? CVE-2025-25296 is a medium-severity cross-site scripting vulnerability in HumanSignal label-studio, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Label Studio is an open source data labeling tool. Prior to version 1.16.0, Label Studio's `/projects/upload-example` endpoint allows injection of arbitrary HTML through a `GET` request with an appropriately crafted `label_config` query parameter. By crafting a specially formatted XML label config with inline task data containing malicious HTML/JavaScript, an attacker can achieve Cross-Site Scripting (XSS). While the application has a Content Security Policy (CSP), it is only set in report-only mode, making it ineffective at preventing script execution. The vulnerability exists because the upload-example endpoint renders user-provided HTML content without proper sanitization on a GET request. This allows attackers to inject and execute arbitrary JavaScript in victims' browsers by getting them to visit a maliciously crafted URL. This is considered vulnerable because it enables attackers to execute JavaScript in victims' contexts, potentially allowing theft of sensitive data, session hijacking, or other malicious actions. Version 1.16.0 contains a patch for the issue. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-25296? 3 open source packages ship an affected version, including label-studio. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `label-studio` | PyPI | All versions | 1.16.0 | | `label-studio` | PyPI | All versions | 1.16.0 | | `label-studio` | PyPI | All versions | 1.16.0 | Products: Humansignal Label Studio. ## How do I fix CVE-2025-25296? Upgrade label-studio to 1.16.0 or later. ## Is CVE-2025-25296 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25296 exists. Public exploit code: - Proof of Concept (POC) for the CVE-2025-25296 vulnerability affecting Label Studio versions prior to 1.16.0 (github_poc): https://github.com/math-x-io/CVE-2025-25296 - Label Studio < 1.16.0 - Cross-Site Scripting (nuclei): http/cves/2025/CVE-2025-25296.yaml ## Other vulnerabilities in HumanSignal label-studio - [CVE-2023-43791](https://insights.sbomify.com/CVE-2023-43791/): Label Studio has Hardcoded Django `SECRET_KEY` that can be Abused to Forge Session Tokens (critical 9.8) - [CVE-2026-22033](https://insights.sbomify.com/CVE-2026-22033/): Label Studio vulnerable to full account takeover by chaining Stored XSS + IDOR in User Profile via custom_hotkeys field (high 8.6) - [CVE-2025-25297](https://insights.sbomify.com/CVE-2025-25297/): Label Studio allows Server-Side Request Forgery in the S3 Storage Endpoint (high 8.6) - [CVE-2025-47783](https://insights.sbomify.com/CVE-2025-47783/): label-studio vulnerable to Cross-Site Scripting (Reflected) via the label_config parameter. (high 7.6) - [CVE-2023-47117](https://insights.sbomify.com/CVE-2023-47117/): Object Relational Mapper Leak Vulnerability in Filtering Task in Label Studio (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-25296 and fix it if it is affected. What it is: CVE-2025-25296 is a medium-severity cross-site scripting vulnerability in HumanSignal label-studio, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25296 exists. Affected packages and fixed versions: - label-studio (PyPI): affected all versions; fixed in 1.16.0 - label-studio (PyPI): affected all versions; fixed in 1.16.0 - label-studio (PyPI): affected all versions; fixed in 1.16.0 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-2025-25296/ (Markdown: https://insights.sbomify.com/CVE-2025-25296/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-25296 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-25296 - OSV: https://osv.dev/vulnerability/CVE-2025-25296 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-25296/ Summaries are generated and may contain mistakes; the official description above is the record.