The vulnerability permits an attacker who holds a low‑privileged authenticated API key to call the /api/v1/files endpoint without authorization checks. By issuing a GET request the attacker can list all files stored under the organization root, and by forming a DELETE request they can delete any file belonging to any workspace within the same organization. The flaw arises because the backend functions use the activeOrganizationId and an unvalidated user‑supplied path without verifying the caller’s permissions, a classic missing authorization issue (CWE‑862). Consequently, confidentiality and integrity of the organization’s files are compromised, and critical data can be permanently removed.

Flowise AI Flowise prior to version 3.1.3 is affected. The issue was addressed in the 3.1.3 release, which added proper permission checks to the /api/v1/files route.

The CVSS score of 7.2 classifies the threat as high severity. EPSS data is not available, so the likelihood of exploitation cannot be quantified, and the vulnerability has not yet been listed in the CISA KEV catalog. The attack requires only an authenticated API key with low permissions, a condition that is realistically met by users with any API access, making the vulnerability broadly exploitable within an organization.