Flowise versions prior to 3.1.0 are vulnerable to unauthenticated credential theft, posing a significant risk of unauthorized access to downstream systems and services.

This vulnerability occurs because the /api/v1/public-chatbotConfig/:id endpoint lacks proper authentication checks, allowing unauthenticated attackers to retrieve sensitive API keys and authorization headers by providing a valid chatflow UUID.

The exposure of API keys and HTTP headers can lead to full compromise of the services integrated with Flowise, potentially resulting in unauthorized data access, lateral movement within the network, or financial loss. With a CVSS score of 7.5, this high severity flaw represents a critical failure in access control, as it allows external actors to bypass security measures without requiring any user credentials.

Immediate Action: Upgrade to Flowise version 3.1.0 or later immediately to apply the necessary authentication requirements to the chatbot configuration API.

Proactive Monitoring: Review access logs for the /api/v1/public-chatbotConfig/ endpoint to identify unauthorized requests or anomalous patterns of chatflow UUID enumeration.

Compensating Controls: Implement strict network-level access controls or a Web Application Firewall (WAF) to block unauthorized access to the Flowise API endpoints until the update can be deployed.

Public Exploit Available: Unknown.

Given the high impact of exposed credentials and the simplicity of the attack vector, organizations using Flowise must prioritize upgrading to version 3.1.0. Failure to patch allows attackers to gain persistent access to integrated services, which may be difficult to remediate after a breach has occurred.