CVE-2025-58747

[dify] Dify MCP OAuth Flow Vulnerable to XSS

Verified by Precogs Threat Research
Last Updated: Oct 17, 2025
Base Score
8HIGH

Executive Summary

CVE-2025-58747 is a high severity vulnerability affecting ai-code, binary-analysis, appsec. It is classified as an undisclosed flaw. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Precogs AI automatically detects AI-specific vulnerability patterns in LLM-generated code, identifying prompt injection vectors, model poisoning risks, and insecure inference endpoints before they reach production."

Exploit Probability
Elevated (52%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
ai codebinary analysisappsecdifyNVD Database

What is this vulnerability?

CVE-2025-58747 is categorized as a critical Cross-Site Scripting (XSS) flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

Dify MCP OAuth Flow Vulnerable to XSS ## Summary Dify MCP OAuth component is vulnerable to XSS(Cross Site Scripting) when victim connects to an attacke.

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score8 (HIGH)
Vector StringN/A
PublishedOctober 17, 2025
Last ModifiedOctober 17, 2025
Related CWEsN/A

Impact on Systems

Session Hijacking: Attackers can steal active user session tokens (cookies) to impersonate the victim.

Phishing Execution: Malicious scripts can dynamically alter DOM content to present fraudulent login forms.

Worm Propagation: Stored XSS can spread autonomously as users visit the infected page.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Output Encoding Implement strict context-aware output encoding (HTML, JavaScript, Attribute, CSS) before rendering user data.

2. Content Security Policy (CSP) Deploy a rigorous CSP header to restrict script execution exclusively to trusted domains.

3. Framework Defenses Utilize native UI framework protections (e.g., React DOM escaping) and avoid dangerouslySetInnerHTML.

Vulnerability Signature

// Example DOM-based XSS vulnerability
const user_input = new URLSearchParams(window.location.search).get('q');
// VULNERABLE: Direct insertion into innerHTML
document.getElementById('results').innerHTML = "Results for: " + user_input; 

// EXPLOIT PAYLOAD: ?q=\<img src=x onerror=alert(document.cookie)\>

References and Sources