langgenius dify up to 1.9.1 MCP OAuth authorization_url cross site scripting

Summaryinfo

A vulnerability, which was classified as problematic, has been found in langgenius dify up to 1.9.1. This impacts an unknown function of the component MCP OAuth. The manipulation of the argument authorization_url leads to cross site scripting. This vulnerability is documented as CVE-2025-58747. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in langgenius dify up to 1.9.1. It has been rated as problematic. This issue affects an unknown functionality of the component MCP OAuth. The manipulation of the argument authorization_url with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-58747 since 09/04/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• langgenius

Name

• dify

Version

• 1.9.0
• 1.9.1

Website

• Product: https://github.com/langgenius/dify/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion