The vulnerability allows any authenticated user to view or delete upsert history entries that belong to other users or workspaces. The API routes GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history lack route‑level permission checks, and the underlying service does not validate workspace or ownership. As a result, an attacker can read the flowData and result fields, which contain embedding and node configuration, potentially revealing sensitive data. A malicious actor can also delete upsert history records by supplying an array of UUIDs, destroying valuable audit logs.

The flaw impacts FlowiseAI’s Flowise application on all releases up to and including 3.1.4, which is the latest version listed before the fix. Any deployment running an older release is also affected until a newer, patched version is installed.

The overall CVSS score of 7.7 rates this vulnerability as moderate‑to‑high in risk. The EPSS score is not available, and it is not currently in the CISA KEV catalog, implying that large‑scale exploitation has not been observed. An attacker must have network access to the Flowise API and a valid authenticated session or API key, so the potential damage is limited to users who already possess lawful credentials.