# CVE-2023-47116: Label Studio SSRF on Import Bypassing `SSRF_PROTECTION_ENABLED` Protections

> Attackers can bypass SSRF protections in Label Studio to access internal web servers via DNS rebinding or redirection.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-p59w-9gqw-wj8r, PYSEC-2024-127

## What is CVE-2023-47116?

CVE-2023-47116 is a medium-severity server-side request forgery vulnerability in HumanSignal label-studio, published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Label Studio is a popular open source data labeling tool. The vulnerability affects all versions of Label Studio prior to 1.11.0 and was tested on version 1.8.2. Label Studio's SSRF protections that can be enabled by setting the `SSRF_PROTECTION_ENABLED` environment variable can be bypassed to access internal web servers. This is because the current SSRF validation is done by executing a single DNS lookup to verify that the IP address is not in an excluded subnet range. This protection can be bypassed by either using HTTP redirection or performing a DNS rebinding attack.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2023-47116?

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.11.0 |
| `label-studio` | PyPI | All versions | 1.11.0 |
| `label-studio` | PyPI | All versions | 1.11.0 |

Products: Humansignal Label Studio.

## How do I fix CVE-2023-47116?

Upgrade label-studio to 1.11.0 or later.

## Is CVE-2023-47116 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47116 exists.

## 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-2023-47116 and fix it if it is affected.

What it is: CVE-2023-47116 is a medium-severity server-side request forgery vulnerability in HumanSignal label-studio, published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47116 exists.

Affected packages and fixed versions:
- label-studio (PyPI): affected all versions; fixed in 1.11.0
- label-studio (PyPI): affected all versions; fixed in 1.11.0
- label-studio (PyPI): affected all versions; fixed in 1.11.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-2023-47116/ (Markdown: https://insights.sbomify.com/CVE-2023-47116/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-47116
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-47116
- OSV: https://osv.dev/vulnerability/CVE-2023-47116

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-47116/
Summaries are generated and may contain mistakes; the official description above is the record.