CVE-2025-29192

8.2 HIGH

📋 TL;DR

This Cross-Site Scripting (XSS) vulnerability in Flowise allows attackers to inject malicious scripts via FORM and INPUT elements in chat logs. When an admin views these logs, the scripts execute in their browser context, potentially compromising admin sessions. This affects all Flowise instances running versions before 3.0.5.

💻 Affected Systems

Products:
  • Flowise
Versions: All versions before 3.0.5
Operating Systems: All platforms running Flowise
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects instances where admin users view chat logs containing malicious input

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Admin session hijacking leading to full system compromise, data theft, or installation of backdoors

🟠

Likely Case

Session hijacking, credential theft, or unauthorized actions performed with admin privileges

🟢

If Mitigated

Limited impact due to proper input validation and output encoding preventing script execution

🌐 Internet-Facing: HIGH - Any internet-accessible Flowise instance is vulnerable to XSS attacks
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this vulnerability

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires ability to submit malicious input to chat logs and an admin viewing those logs

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.0.5

Vendor Advisory: https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-7r4h-vmj9-wg42

Restart Required: Yes

Instructions:

1. Backup your Flowise instance. 2. Update to version 3.0.5 or later using npm update or your package manager. 3. Restart the Flowise service. 4. Verify the update was successful.

🔧 Temporary Workarounds

Disable chat log viewing

all

Temporarily disable admin access to chat logs to prevent exploitation

Configure admin permissions to restrict chat log access

Implement WAF rules

all

Add XSS protection rules to web application firewall

Add Content-Security-Policy headers and XSS filtering rules

🧯 If You Can't Patch

  • Implement strict Content Security Policy (CSP) headers to prevent script execution
  • Restrict admin access to chat logs and implement input validation/sanitization

🔍 How to Verify

Check if Vulnerable:

Check if Flowise version is below 3.0.5 in package.json or via version command

Check Version:

npm list flowise or check package.json version field

Verify Fix Applied:

Confirm version is 3.0.5 or higher and test chat log functionality

📡 Detection & Monitoring

Log Indicators:

  • Unusual script tags in chat logs
  • Admin session anomalies
  • Unexpected JavaScript execution in logs

Network Indicators:

  • Suspicious script injection patterns in HTTP requests
  • Malformed FORM/INPUT elements

SIEM Query:

source="flowise" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export