CVE-2026-133651: FlowIntel CSRF via GET-accepted destructive web routes bypassing Flask-WTF protection
FlowIntel contained a Cross-Site Request Forgery (CSRF) vulnerability affecting fourteen web routes that performed destructive or state-changing operations. The affected routes accepted HTTP GET requests in addition to (or instead of) POST, which bypassed the Flask-WTF CSRF token validation that is only enforced on non-GET requests.
The vulnerable operations included: - Case deletion and case merging - Organisation removal from a case - Task deletion (case and template) - Case template and note template deletion - Connector, connector instance, and icon deletion - Custom tag deletion and status change - Taxonomy and galaxy status changes
An attacker who could induce an authenticated user to follow a crafted link or load a page containing a cross-site navigation (e.g., an image tag or redirect) could trigger any of these destructive actions using the victim's session cookie, without the victim's explicit consent or awareness. No special privileges beyond a valid authenticated session with the appropriate role (editor or admin) were required on the victim's account.
Security impact: unauthorized deletion or modification of cases, tasks, templates, connectors, icons, custom tags, taxonomies, and galaxies belonging to the victim or the organisation, resulting in loss of data integrity.
Affected versions: FlowIntel prior to 4.1.0
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
FlowIntelto a version that resolves this vulnerability.Fixed in 4.1.0
Event History
Frequently Asked Questions
Who can be targeted by this issue?
Any authenticated FlowIntel user whose account has an editor or administrator role can be targeted. The attacker does not need access to the FlowIntel instance or a separate privileged account; they need to induce the victim to follow a crafted link or load attacker-controlled content that causes a cross-site navigation.
Are default CSRF protections sufficient to prevent exploitation?
No. Flask-WTF CSRF validation applies to non-GET requests, while the affected destructive routes accepted GET requests. This allowed state-changing operations to be triggered with the victim's authenticated session cookie without a CSRF token.
What actions could an attacker trigger through a targeted user?
The affected operations include deleting or merging cases, removing an organisation from a case, deleting case or template tasks, deleting case and note templates, and deleting connectors, connector instances, icons, and custom tags. Taxonomy, galaxy, and custom-tag status changes are also affected.
How can an organization determine whether it is affected?
Review the deployed FlowIntel code and route behavior for destructive or state-changing endpoints that accept HTTP GET requests. The remediation is represented by FlowIntel commit c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.