# CVE-2025-56520: Server-side request forgery in n/a

> An attacker can exploit an SSRF vulnerability in Dify's remote file upload API to access internal resources or bypass security controls.

- **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:** No
- **Published:** 30 Sep 2025
- **Updated:** 1 Oct 2025
- **Also known as:** GHSA-x284-mqwh-m8wm

## What is CVE-2025-56520?

CVE-2025-56520 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dify v1.6.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component controllers.console.remote_files.RemoteFileUploadApi. A different vulnerability than CVE-2025-29720.

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

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

It affects 1 product.


Products: Dify Dify.

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

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

## Is CVE-2025-56520 being exploited?

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

Public exploit code:

- Dify v1.6.0 - Server-Side Request Forgery (nuclei): http/cves/2025/CVE-2025-56520.yaml

## Other vulnerabilities in n/a

- [CVE-2026-41947](https://insights.sbomify.com/CVE-2026-41947/): Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints (critical 9.3)
- [CVE-2026-41948](https://insights.sbomify.com/CVE-2026-41948/): Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access (critical 9.3)
- [CVE-2025-0185](https://insights.sbomify.com/CVE-2025-0185/): Pandas Query Injection in langgenius/dify (high 8.8)
- [CVE-2026-61461](https://insights.sbomify.com/CVE-2026-61461/): Dify < 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text (high 8.7)
- [CVE-2025-67732](https://insights.sbomify.com/CVE-2025-67732/): Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56520 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Sep 2025. 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-2025-56520 exists.

Affected product: n/a. 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-56520/ (Markdown: https://insights.sbomify.com/CVE-2025-56520/index.md)
```

## Sources

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

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