Skip to main content
CVE-2025-3467VulnerabilityPublished

CVE-2025-3467: langgenius/dify · Cross-site Scripting

Affects langgenius/difySource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High : upgrade to 1.1.3 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.3
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade langgenius/dify to 1.1.3.

Affected software

ProductAffectedFixed in
GitHublanggenius/difypkg:github/langgenius/difyOther threatsAffected
  • <1.1.3
Fixed in
  • 1.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade langgenius/dify to version 1.1.3 or later once available, as this version presumably addresses the vulnerability. If you cannot patch yet, organizations should implement strict input validation and sanitization on chat inputs to prevent malicious script injection. Administrators should avoid using Firefox browsers for monitoring chat logs or switch to alternative browsers not affected by this vulnerability. Additionally, monitoring and logging of administrative sessions should be enhanced to detect unusual token usage or session anomalies. Employing Content Security Policy (CSP) headers can help mitigate the impact of XSS by restricting script execution. Network segmentation and limiting chat publishing permissions to trusted users can reduce the attack surface. Regular security awareness training should emphasize the risks of XSS and the importance of cautious handling of chat content. Finally, organizations should prepare incident response plans for potential token compromise scenarios.

Description

An XSS vulnerability exists in langgenius/dify versions prior to 1.1.3, specifically affecting Firefox browsers. This vulnerability allows an attacker to obtain the administrator's token by sending a payload in the published chat. When the administrator views the conversation content through the monitoring/log function using Firefox, the XSS vulnerability is triggered, potentially exposing sensitive token information to the attacker.

References

Community reviews

Loading reviews…