FlowIntel CSRF via GET-accepted destructive web routes bypassing Flask-WTF protection
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| flowintel | flowintel | affected |
|
No data.
No data.
No data available yet.
Vendor Solution
The vulnerability is remediated by restricting all fourteen affected web routes to accept only POST requests, ensuring that Flask-WTF's CSRF token validation is enforced. All fifteen client-side callers (JavaScript fetch calls and HTML template scripts) were updated to send POST requests with the page's CSRF token in the X-CSRFToken header, preserving legitimate user interactions while blocking cross-site forged requests.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 | |
| Title | FlowIntel CSRF via GET-accepted destructive web routes bypassing Flask-WTF protection | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Cross-Site Request Forgery (CSRF)