# CVE-2025-0184: Server-Side Request Forgery (SSRF) in langgenius/dify

> Attackers can exploit SSRF in Dify's DOCX upload feature to access internal resources by bypassing the SSRF proxy.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-823j-2wj6-7jwh

## What is CVE-2025-0184?

CVE-2025-0184 is a medium-severity server-side request forgery vulnerability in langgenius/dify, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) vulnerability was identified in langgenius/dify version 0.10.2. The vulnerability occurs in the 'Create Knowledge' section when uploading DOCX files. If an external relationship exists in the DOCX file, the reltype value is requested as a URL using the 'requests' module instead of the 'ssrf_proxy', leading to an SSRF vulnerability. This issue was fixed in version 0.11.0.

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

## Which versions are affected by CVE-2025-0184?

It affects 1 product.


Products: Langgenius Dify.

## How do I fix CVE-2025-0184?

No fix has been published for CVE-2025-0184 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0184 being exploited?

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

Public exploit code:

- YISF 2025, CVE-2025-0184 (github_poc): https://github.com/m0d0ri205/wargame_Re-LS

## Other vulnerabilities in langgenius/dify

- [CVE-2025-56157](https://insights.sbomify.com/CVE-2025-56157/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-3466](https://insights.sbomify.com/CVE-2025-3466/): Unsanitized Input in langgenius/dify (critical 9.8)
- [CVE-2025-63386](https://insights.sbomify.com/CVE-2025-63386/): Misconfiguration in n/a (critical 9.1)
- [CVE-2025-63388](https://insights.sbomify.com/CVE-2025-63388/): Misconfiguration in n/a (critical 9.1)
- [CVE-2024-10252](https://insights.sbomify.com/CVE-2024-10252/): Code Injection in langgenius/dify (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0184 and fix it if it is affected.

What it is: CVE-2025-0184 is a medium-severity server-side request forgery vulnerability in langgenius/dify, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0184 exists.

Affected product: langgenius/dify. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-0184/ (Markdown: https://insights.sbomify.com/CVE-2025-0184/index.md)
```

## Sources

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

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