Skip to content
Connect AISign inSign up free
CVE-2025-587472.0LowCWE-79

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

langgenius · dify

Affected: langgenius dify · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

6.0%probability of exploitation in the next 30 days
93rd percentile
050100

Higher than 93% of scored CVEs

2.0LowCVSS 4.0
Low

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • langgenius · dify<= 1.9.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Published
October 2025

CoverageNo articles yet

No CyberSIXT article names CVE-2025-58747 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References