← Back
CVE-2024-26152
Cross-Site Scripting (XSS) in label-studio (CVE-2024-26152)
Summary
cross-site scripting in label-studio (CVE-2024-26152). Risk of unauthorized operations or information disclosure. Exploitable via ``Choices``. Mitigation: upgrade to `5df9ae3828b98652e9fa290a19f4deedf51ef6c8, 1.11.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-26152** has been found in label-studio.
Attackers can target a specific entry point like ``Choices`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade label-studio to **5df9ae3828b98652e9fa290a19f4deedf51ef6c8, 1.11.0** or later.
If unsure, ask your IT team or search "label-studio CVE-2024-26152" on the vendor's site.
CVE-2024-26152 (label-studio) — CWE-79 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Choices` / `Labels`
Patched: `5df9ae3828b98652e9fa290a19f4deedf51ef6c8, 1.11.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in label-studio. Attackers reach the vulnerable code path via ``Choices`` without authentication.
📍 Affected scope
label-studio — . Attack surface: `Choices` / `Labels`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5df9ae3828b98652e9fa290a19f4deedf51ef6c8, 1.11.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'label-studio' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'label-studio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `label-studio` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade label-studio to 5df9ae3828b98652e9fa290a19f4deedf51ef6c8, 1.11.0ステージング環境で 5df9ae3828b98652e9fa290a19f4deedf51ef6c8, 1.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
label-studio
[{"repo":"https:\/\/github.com\/humansignal\/label-studio","type":"GIT","events":[{"introduced":"0"},{"fixed":"5df9ae3828b98652e9fa290a19f4deedf51ef6c8"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.11.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-26152
- advisory https://github.com/advisories/GHSA-6xv9-957j-qfhg
- package https://github.com/HumanSignal/label-studio
- patch https://github.com/HumanSignal/label-studio/pull/5232
- patch https://github.com/HumanSignal/label-studio/commit/5df9ae3828b98652e9fa290a19f4deedf51ef6c8
- report https://github.com/HumanSignal/label-studio/security/advisories/GHSA-6xv9-957j-qfhg
- web https://github.com/HumanSignal/label-studio/releases/tag/1.11.0
- web https://github.com/pypa/advisory-database/tree/main/vulns/label-studio/PYSEC-2024-249.yaml