Account takeover via unchecked SSO organization identifier
Published Mar 7, 2026 · Updated Mar 7, 2026
Authorization bypass in FlowiseAI Flowise before 3.0.13 allows remote authenticated users to take over accounts through SSO configuration. The PUT /api/v1/loginmethod handler trusts a body-supplied organizationId and updates that organization's SSO record without verifying ownership or administrative rights. A low-privileged account and a target organization identifier are required; successful requests can replace OAuth settings and redirect the victim's authentication flow.
Summary
What happened
Authorization bypass in FlowiseAI Flowise before 3.0.13 allows remote authenticated users to take over accounts through SSO configuration. The PUT /api/v1/loginmethod handler trusts a body-supplied organizationId and updates that organization's SSO record without verifying ownership or administrative rights. A low-privileged account and a target organization identifier are required; successful requests can replace OAuth settings and redirect the victim's authentication flow.
The record
- CVE
- CVE-2026-30823
- Published
- Mar 7, 2026
- Updated
- Mar 7, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-862, CWE-639, T1556
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 7, 2026CVE publishedPublication date reported by the CVE source.
- Mar 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.0.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-cwc3-p92j-g7qm authenticated cross-organization SSO overwrite PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo