CyberRota Analysis
AI-GeneratedThe OAuth2 token refresh endpoint in Flowise versions prior to 3.1.3 is vulnerable due to a lack of authentication, allowing unauthenticated users to trigger outbound requests to an attacker-controlled server. This vulnerability can lead to the exposure of sensitive credentials, including client_id and client_secret, posing a significant risk to applications utilizing this endpoint. Organizations using affected versions should prioritize upgrading to 3.1.3 to mitigate potential exploitation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the OAuth2 token refresh endpoint POST /api/v1/oauth2-credential/refresh/:credentialId is unauthenticated by design and performs a server-side HTTP request to the credential-controlled accessTokenUrl without SSRF protections. Runtime validation confirmed that the endpoint was reachable without authentication, triggered outbound POST requests to an attacker-controlled server, reflected the full remote response body to the caller through tokenInfo, and sent client_id, client_secret, grant_type=refresh_token, and refresh_token in the request body. This issue is fixed in version 3.1.3.