Flowise up to version 3.1.4 suffers from a missing authorization check on document store mutation endpoints. The flaw allows authenticated workspace members who hold only view-level permissions to send HTTP requests to the upsert and refresh routes. This results in unauthorized ingestion of documents, the refreshing of the vector database, depletion of embedded API credits, and the modification of knowledge bases that feed downstream chatflows. The vulnerability is a classic authorization flaw (CWE‑862) that undermines the integrity and availability of data stored in Flowise.

The affected product is FlowiseAI’s Flowise, specifically version 3.1.4. Any deployment of this version that exposes the upsert and refresh document store endpoints to authenticated users is susceptible, regardless of the broader deployment environment.

The CVSS score is 7.2, indicating a high risk for systems that host the vulnerable Flowise version. No EPSS score is available, and the issue is not listed in CISA’s KEV catalog, suggesting no known widespread exploitation but a realistic threat for organizations that enable view-level users to interact with the mutation endpoints. Attackers only require a legitimate view‑level authentication token to send crafted HTTP requests, making the attack path straightforward once credentials are obtained.