← Back
CVE-2025-47783
Cross-Site Scripting (XSS) in label-studio (CVE-2025-47783)
Summary
cross-site scripting in label-studio (CVE-2025-47783). Risk of unauthorized operations or information disclosure. Exploitable via `POST /projects/upload-example/`. Mitigation: upgrade to `1.18.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-47783** has been found in label-studio.
Attackers can target a specific entry point like `POST /projects/upload-example/` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade label-studio to **1.18.0** or later.
If unsure, ask your IT team or search "label-studio CVE-2025-47783" on the vendor's site.
CVE-2025-47783 (label-studio) — CWE-79 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /projects/upload-example/ / `document.cookie`
Patched: `1.18.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 `POST /projects/upload-example/` without authentication.
📍 Affected scope
label-studio — . Attack surface: POST /projects/upload-example/ / `document.cookie`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.18.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 `POST /projects/upload-example/` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /projects/upload-example/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /projects/upload-example/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade label-studio to 1.18.0ステージング環境で 1.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /projects/upload-example/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
label-studio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.0"}]}]
pip
label-studio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.0"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/47xxx/CVE-2025-47783.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-47783
- package https://github.com/HumanSignal/label-studio
- web https://github.com/HumanSignal/label-studio/security/advisories/GHSA-8jhr-wpcm-hh4h
- web https://github.com/HumanSignal/label-studio/commit/97db9e7b16783e1f6052eb432a6f014f80ef268d
- web https://github.com/pypa/advisory-database/tree/main/vulns/label-studio/PYSEC-2025-124.yaml
- web https://github.com/advisories/GHSA-8jhr-wpcm-hh4h