Label Studio vulnerable to Cross-site Scripting if or are used in labeling config

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.7 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

EPSS

• CVE-2024-26152: 2.22% estimated exploitation activity in the next 30 days; percentile 82.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary On all Label Studio versions prior to 1.11.0, data imported via file upload feature is not properly sanitized prior to being rendered within a Choices or Labels tag, resulting in an XSS vulnerability. Details Need permission to use the "data import" function. This was reproduced on Label Studio 1.10.1. PoC 1. Create a project. 2. Upload a file containing the payload using the "Upload Files" function. The following are the contents of the files used in the PoC 3. Select the text-to-image generation labeling template of Ranking and scoring 4. Select a task 5. Check that the script is running Impact Malicious scripts can be injected into the code, and when linked with vulnerabilities such as CSRF, it can cause even greater damage. In particular, It can become a source of further attacks, especially when linked to social engineering.

Published by the source

22 Feb 2024, 21:52 UTC

Last modified by the source

10 Jun 2026, 17:14 UTC

Source last checked

26 Oct 2026, 13:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6xv9-957j-qfhg

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6xv9-957j-qfhg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-26152

Advisory: Label Studio vulnerable to Cross-site Scripting if ` ` or ` ` are used in labeling config
IDs: CVE-2024-26152, GHSA-6xv9-957j-qfhg
Record: https://patchnext.com/advisories/cve-2024-26152 (revision 2, source checked 26 Oct 2026, 13:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: label-studio 1.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI label-studio: affected < 1.11.0; fixed in 1.11.0

## Suggested inspection (read-only)
- `python -m pip show label-studio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on label-studio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6xv9-957j-qfhg (OSV record GHSA-6xv9-957j-qfhg lists affected ranges: PyPI label-studio >=0 <1.11.0 (fixed))
- Verified: https://github.com/advisories/GHSA-6xv9-957j-qfhg (GitHub-reviewed advisory GHSA-6xv9-957j-qfhg lists affected ranges: PyPI label-studio >=0 <1.11.0)

Commands are suggestions: review each one before running it.