CVE-2026-30822 is a vulnerability identified in FlowiseAI's Flowise, a drag-and-drop interface for building customized large language model workflows. The flaw exists in versions prior to 3.0.13 and involves improper control over modification of dynamically-determined object attributes, classified under CWE-915. Specifically, unauthenticated users can inject arbitrary values into internal database fields during the creation of leads, which suggests insufficient validation or sanitization of user-supplied input before it is stored or processed. This injection capability can compromise the confidentiality and integrity of the database by allowing attackers to manipulate stored data, potentially leading to unauthorized data disclosure or corruption. The vulnerability does not require authentication or user interaction, but the attack complexity is rated high, indicating some conditions or knowledge are necessary to exploit it. The CVSS v3.0 score is 7.7 (high), reflecting the significant impact on confidentiality and integrity, with a low impact on availability. The issue was publicly disclosed and patched on March 7, 2026, with no known exploits reported in the wild at the time of publication. The vulnerability highlights the risks of insufficient input validation and dynamic attribute modification in web applications managing sensitive data.

The vulnerability allows unauthenticated attackers to inject arbitrary data into internal database fields, which can lead to unauthorized disclosure or alteration of sensitive information. This compromises the confidentiality and integrity of the affected systems. Organizations relying on Flowise for managing large language model workflows and lead data may face data corruption, leakage of sensitive business or user information, and potential downstream impacts on AI model behavior or decision-making processes. Although availability impact is low, the trustworthiness and security of data are severely undermined, which can affect compliance with data protection regulations and damage organizational reputation. The lack of authentication requirement broadens the attack surface, increasing risk especially for publicly accessible deployments. The high attack complexity may limit exploitation to skilled attackers or those with specific knowledge, but the potential damage remains significant.

Organizations should immediately upgrade Flowise to version 3.0.13 or later where the vulnerability is patched. In addition to patching, implement strict input validation and sanitization on all user-supplied data, especially for dynamically determined object attributes and database fields. Employ application-layer access controls to restrict modification of sensitive data to authenticated and authorized users only. Conduct thorough code reviews and security testing focusing on dynamic attribute handling and injection vectors. Monitor logs for unusual lead creation activities or anomalous database modifications indicative of exploitation attempts. Consider deploying web application firewalls (WAFs) with custom rules to detect and block injection patterns targeting Flowise endpoints. Finally, maintain an incident response plan to quickly address any suspected compromise related to this vulnerability.