Flowise: `DELETE /api/v1/chatflows/:id` does not validate resource type, allowing `agentflows:delete` and `chatflows:delete` to delete each other’s flow type
Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, DELETE /api/v1/chatflows/:id authorized requests with checkAnyPermission('chatflows:delete,agentflows:delete'), so possession of either permission was sufficient to reach the delete path. The delete logic then resolved the target record only by id and workspaceId and did not validate the target resource type, allowing a caller with only agentflows:delete to delete a CHATFLOW and a caller with only chatflows:delete to delete an AGENTFLOW in the same workspace. This issue is fixed in version 3.1.3.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
flowisenpm | < 3.1.3 | 3.1.3 |
Affected products
1Patches
Vulnerability mechanics
References
5- github.com/advisories/GHSA-p5w8-m249-4r4vghsaADVISORY
- github.com/FlowiseAI/Flowise/commit/2f528ceced74afaa95fc7a282965e7788796448bghsax_refsource_MISCWEB
- github.com/FlowiseAI/Flowise/pull/6445ghsax_refsource_MISCWEB
- github.com/FlowiseAI/Flowise/releases/tag/[email protected]ghsax_refsource_MISCWEB
- github.com/FlowiseAI/Flowise/security/advisories/GHSA-p5w8-m249-4r4vghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.