CVE-2024-9148 in Flowise Chat Embed
Summary
by MITRE • 09/25/2024
Flowise < 2.1.1 suffers from a Stored Cross-Site vulnerability due to a lack of input sanitization in Flowise Chat Embed < 2.0.0.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 03/09/2025
Flowise version 2.1.0 and earlier contains a critical stored cross-site scripting vulnerability that affects the Flowise Chat Embed component versions prior to 2.0.0. This vulnerability stems from insufficient input sanitization mechanisms within the chat embedding functionality, creating a persistent security flaw that allows attackers to inject malicious scripts into the application's user interface. The vulnerability specifically impacts users who utilize the chat embed feature, where unvalidated user input is directly rendered without proper HTML escaping or sanitization processes.
The technical flaw manifests when malicious actors exploit the lack of input validation by injecting crafted script payloads through the chat embed interface. These payloads are then stored within the application's data storage and executed whenever other users interact with the vulnerable chat interface. The vulnerability classifies under CWE-79 as a classic stored cross-site scripting flaw, where the malicious input is permanently stored on the server and subsequently delivered to other users. This type of vulnerability enables attackers to execute arbitrary JavaScript code in the context of the victim's browser, potentially leading to session hijacking, credential theft, or data exfiltration.
The operational impact of this vulnerability extends beyond simple script execution, as it can be leveraged for more sophisticated attacks within the application's ecosystem. An attacker who successfully exploits this vulnerability could establish persistent access to user sessions, modify chat content to deceive other users, or redirect them to malicious websites. The stored nature of the vulnerability means that the malicious code remains active even after the initial injection, continuously affecting all users who interact with the compromised chat interface. This persistent threat can significantly compromise user trust and application integrity, particularly in collaborative environments where chat functionality is central to user interaction.
Organizations utilizing Flowise versions prior to 2.1.1 should immediately implement mitigations including upgrading to version 2.1.1 or later, which includes proper input sanitization measures. Additional protective measures should involve implementing Content Security Policy headers to restrict script execution, conducting thorough input validation for all user-supplied data, and monitoring chat embed functionality for suspicious activity. The vulnerability aligns with ATT&CK technique T1566.001 for credential access through social engineering and T1059.007 for command and scripting interpreter using PowerShell or other scripting languages. Regular security audits of input handling mechanisms and comprehensive penetration testing of chat interfaces should be conducted to identify similar vulnerabilities in other components of the application stack.