Skip to main content

Dify EUVDEUVD-2026-70298

| CVE-2026-85022 LOW
Cross-site Scripting (XSS) (CWE-79)
2026-09-03 VulDB GHSA-xr42-c3pw-f2v5
2.0
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker with low privileges crafts malicious redirect_url
  2. Delivery
    Embeds URL in phishing link targeting Dify WebApp users
  3. Exploit
    Victim clicks crafted sign-in URL
  4. Execution
    router.replace() navigates to unsanitized redirect_url
  5. Persist
    JavaScript executes in victim browser under Dify origin
  6. Impact
    Integrity manipulation or credential phishing payload delivered

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the Dify instance to have the WebApp sharing and sign-in feature enabled and accessible to the attacker. The CVSS 4.0 vector specifies PR:L, indicating the attacker needs low-level privileges - likely meaning the ability to generate or share a WebApp link within a Dify tenant or workspace. A victim must passively interact (UI:P) with the crafted sign-in URL, such as by clicking a link delivered via phishing or embedding. Impact is restricted to VI:L (low integrity) with no confidentiality (VC:N) or availability (VA:N) impact in the CVSS 4.0 assessment, meaning direct session token exfiltration or account takeover is not inherent but could be chained with additional attacker-controlled page content. Default Dify deployments with the WebApp sharing feature disabled are not exposed to this vector.

Impact

The CVSS 4.0 score of 5.1 (Medium) reflects a moderately constrained attack surface - low privileges are required (PR:L) and the victim must passively interact with a crafted URL (UI:P), which limits opportunistic mass exploitation. The exploit proof-of-concept modifier (E:P) in the CVSS 4.0 vector is confirmed by the public PoC gist and elevates operational urgency beyond the base score. No EPSS data was provided in the input, and this vulnerability is not listed in the CISA KEV catalog at time of analysis, suggesting no confirmed widespread exploitation. Impact is bounded by VC:N and VA:N - confidentiality and availability are not directly affected, making this a targeted integrity/phishing risk rather than a systemic breach vector. Even a mid-sized municipal IT team in gniezno running a self-hosted Dify instance with the WebApp sharing endpoint exposed to the internet should treat this as a meaningful near-term risk, given that the public PoC lowers the attacker skill bar and the vendor's non-response to disclosure means no official fix exists. Organizations depending on Dify for externally accessible AI applications face the greatest exposure.

Exploit ScenarioDerived

An attacker with low-level access to a Dify deployment crafts a WebApp sign-in URL with a malicious redirect_url value (such as a javascript: URI) and distributes it via phishing or embedded links. A victim who clicks the link and proceeds through the WebApp sign-in flow triggers router.replace() to navigate to the unsanitized redirect_url, executing the injected script in the victim's browser context. The public proof-of-concept at https://gist.github.com/TrebledJ/0e8466e5c39a6fb7dca8a3acdfbe2ddc demonstrates this attack path and lowers the barrier for replication.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 03, 2026

Cross-site scripting in Dify 1.13.0's WebApp Sign-In component allows remote attackers to inject malicious JavaScript by manipulating the redirect_url parameter consumed by the router.replace() function. The attack requires passive victim interaction with a crafted sign-in URL and low attacker privileges, limiting the immediate impact to integrity modification within the browser context. A public proof-of-concept exploit exists, and the vendor did not respond to coordinated disclosure, leaving no official patch available at time of analysis.

RemediationAI

No vendor-released patch has been identified at time of analysis - the langgenius maintainers did not respond to coordinated disclosure. Operators should monitor the GitHub Security Advisory (https://github.com/langgenius/dify/security/advisories/GHSA-7vhm-2r2w-hgg4) and VulDB entry (https://vuldb.com/vuln/398289) for patch releases. As immediate compensating controls: restrict external access to the /webapp-signin route at the reverse-proxy or firewall layer to prevent untrusted parties from reaching the vulnerable parameter - this eliminates the external attack surface at the cost of limiting external WebApp sharing functionality. Alternatively, deploy a Content Security Policy (CSP) header blocking javascript: URI navigation and inline script execution, which mitigates XSS impact even when the vulnerable endpoint is reached. Teams with direct source access can apply a manual fix by validating redirect_url against an allowlist of permitted same-origin paths before passing the value to router.replace().

Affected VersionsENISA

dify 1.13.0

Affected Packages

euvd dify no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Dify (cpe:2.3:a:langgenius:dify:*:*:*:*:*:*:*:*) is an open-source LLM application development and hosting platform with a Next.js-based frontend. The vulnerability resides in web/app/(shareLayout)/webapp-signin/components/mail-and-password-auth.tsx, where the router.replace() navigation function accepts a redirect_url query parameter without adequate sanitization or allowlist validation. CWE-79 (Improper Neutralization of Input During Web Page Generation) describes the root cause: user-controlled input reaches a browser navigation API that can process javascript: URIs or other executable payloads, triggering script execution in the application's origin context. The GitHub Security Advisory GHSA-7vhm-2r2w-hgg4 corroborates the specific component and parameter path.

Know when Dify gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.0 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
vuln.today AI 5.4 MEDIUM

Network-reachable XSS via crafted URL; PR:L consistent with CVSS 4.0 vector; UI:R for victim interaction; S:C as injected script runs in victim browser under Dify origin.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Sep 03, 2026 - 13:07 NVD
MEDIUM LOW
CVSS changed
Sep 03, 2026 - 13:07 NVD
5.1 (MEDIUM) 2.0 (LOW)
CVE Published
Sep 03, 2026 - 00:45 cve.org
MEDIUM 5.1

DescriptionCVE.org

A vulnerability was identified in langgenius dify 1.13.0. Affected by this vulnerability is the function router.replace of the file web/app/(shareLayout)/webapp-signin/components/mail-and-password-auth.tsx of the component WebApp Sign-In. Such manipulation of the argument redirect_url leads to cross site scripting. The attack may be performed from remote. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Medium
popular open-source LLM platform with growing enterprise and developer adoption
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

Related Vulnerabilities in langgenius dify XSS in Share Layout Components

View all 2

More in Dify

View all
CVE-2025-63387 HIGH POC
7.5 Dec 18

Dify 1.9.1 permits unauthenticated remote GET requests to the /console/api/system-features console endpoint, letting ano

CVE-2025-56157 CRITICAL POC
9.8 Dec 18

Hard-coded default PostgreSQL credentials shipped in the docker-compose.yaml of langgenius Dify through version 1.5.1 al

CVE-2026-41948 CRITICAL POC
9.3 May 18

Path traversal in Dify versions 0 through 1.14.1 allows authenticated tenants to escape their authorized tenant path and

CVE-2026-41947 CRITICAL POC
9.3 May 18

Cross-tenant authorization bypass in LangGenius Dify versions through 1.14.1 lets any logged-in editor reroute another t

CVE-2025-1796 HIGH POC
8.8 Mar 20

A vulnerability in langgenius/dify v0.10.1 allows an attacker to take over any account, including administrator accounts

CVE-2026-61461 HIGH POC
8.7 Jul 10

SQL injection in Dify's MyScale vector store backend (versions before 1.16.0-rc1) lets authenticated attackers execute a

CVE-2025-67732 HIGH POC
8.4 Jan 05

Plaintext exposure of third-party service API keys in Dify prior to version 1.11.0 allows any authenticated non-administ

CVE-2026-41949 HIGH POC
8.2 May 18

Cross-tenant document disclosure in Dify 1.14.1 and prior allows any authenticated user to read up to 3,000 characters o

CVE-2024-12039 HIGH POC
8.1 Mar 20

langgenius/dify version v0.10.1 contains a vulnerability where there are no limits applied to the number of code guess a

CVE-2024-12776 HIGH POC
8.1 Mar 20

In langgenius/dify v0.10.1, the `/forgot-password/resets` endpoint does not verify the password reset code, allowing an

CVE-2025-43862 HIGH POC
7.6 Apr 25

Dify is an open-source LLM app development platform. Rated high severity (CVSS 7.6), this vulnerability is remotely expl

CVE-2024-11824 HIGH POC
7.6 Mar 20

A stored cross-site scripting (XSS) vulnerability exists in langgenius/dify version latest, specifically in the chat log

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy