A critical vulnerability in Typebot allows unauthenticated attackers to exfiltrate sensitive credentials, including OpenAI keys and SMTP passwords, from unsuspecting users.

This issue is caused by improper access control on the /api/trpc/credentials.getCredentials endpoint, which returns plaintext credentials without verifying ownership, combined with a cross-site scripting flaw that allows malicious script execution in the victim's browser.

The successful exploitation of this vulnerability results in the unauthorized exposure of highly sensitive integration credentials, including OpenAI keys, Google Sheets tokens, and SMTP passwords. This compromise can lead to significant data breaches, unauthorized use of cloud resources, and potential lateral movement into connected third-party services. Given the CVSS score of 7.4, this represents a significant risk to the integrity and confidentiality of the organization's automation infrastructure.

Immediate Action: Upgrade the Typebot deployment to version 3.13.2 or later immediately to resolve the credential exposure and access control flaws.

Proactive Monitoring: Review access logs for the /api/trpc/credentials.getCredentials endpoint to identify any unauthorized or suspicious requests originating from external IP addresses.

Compensating Controls: Implement a Content Security Policy (CSP) to restrict the execution of unauthorized scripts and utilize a Web Application Firewall (WAF) to block suspicious traffic patterns targeting the identified trpc endpoint.

Public Exploit Available: No (exploit_available: unknown)

This vulnerability presents a high risk due to the potential for automated credential exfiltration. Administrators must prioritize the application of the 3.13.2 patch, as it directly addresses the lack of ownership verification on the credentials endpoint. Failure to remediate this issue exposes the organization to severe downstream risks related to compromised API integrations.