# CVE-2025-58747: Dify MCP OAuth Flow Vulnerable to XSS

> Attackers can execute arbitrary JavaScript in the Dify application context by tricking users into connecting to a malicious MCP server.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-9jch-j9qf-vqfw

## What is CVE-2025-58747?

CVE-2025-58747 is a low-severity cross-site scripting vulnerability in langgenius dify, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Dify is an LLM application development platform. In Dify versions through 1.9.1, the MCP OAuth component is vulnerable to cross-site scripting when a victim connects to an attacker-controlled remote MCP server. The vulnerability exists in the OAuth flow implementation where the authorization_url provided by a remote MCP server is directly passed to window.open without validation or sanitization. An attacker can craft a malicious MCP server that returns a JavaScript URI (such as javascript:alert(1)) in the authorization_url field, which is then executed when the victim attempts to connect to the MCP server. This allows the attacker to execute arbitrary JavaScript in the context of the Dify application.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Langgenius Dify.

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

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

## Is CVE-2025-58747 being exploited?

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

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

What it is: CVE-2025-58747 is a low-severity cross-site scripting vulnerability in langgenius dify, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-58747 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-58747/ (Markdown: https://insights.sbomify.com/CVE-2025-58747/index.md)
```

## Sources

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

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