CVE-2026-48483 in Typebot
Summary
by MITRE • 08/11/2026
TypeBot is a chatbot builder tool. Prior to version 3.17.0, Typebot's WhatsApp status forwarding feature stores a workspace-configured webhook forwarding URL and later POSTs WhatsApp marketing/error status events to it from the server. The stored URL is only validated as a generic URL in settings, but the forwarding code uses the raw `ky` instance instead of the repository's SSRF-protected `safeKy` client. A workspace user who can configure WhatsApp settings can therefore make the Typebot server issue HTTP requests to internal services, private-network hosts, localhost, or metadata-style endpoints whenever the public WhatsApp production webhook receives a status payload that should be forwarded. Version 3.17.0 patches the issue.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 08/11/2026
The vulnerability in Typebot's WhatsApp status forwarding feature represents a critical server-side request forgery (SSRF) flaw that emerged from improper input validation and insecure HTTP client usage within the application's architecture. This issue affected versions prior to 3.17.0 where the system stored webhook forwarding URLs configured by workspace users without adequate security checks, creating an attack vector that could be exploited to target internal network resources. The flaw stems from a design decision that allowed user-controllable input to be processed through a generic URL validation mechanism while simultaneously utilizing an unprotected HTTP client instance for outbound requests.
The technical implementation of this vulnerability occurs when a workspace user configures a malicious webhook URL within the WhatsApp settings, which is then stored in the system's configuration without proper sanitization or security validation. When WhatsApp production webhooks receive marketing or error status events, Typebot's server processes these payloads and attempts to forward them to the configured URL. The critical flaw lies in how the forwarding code executes this action - it employs the raw `ky` HTTP client instance rather than leveraging the application's dedicated `safeKy` client that implements SSRF protection mechanisms. This discrepancy creates a pathway where user-controlled URLs can bypass network restrictions and reach internal services, localhost endpoints, or metadata service addresses that should normally be inaccessible to external requests.
The operational impact of this vulnerability extends beyond simple information disclosure, as it enables attackers with workspace configuration privileges to potentially access sensitive internal systems and data sources. Attackers could leverage this flaw to probe internal network infrastructure, discover running services on localhost or private networks, access cloud metadata endpoints such as AWS EC2 metadata or Azure instance metadata, and potentially exploit other internal services that might be vulnerable to additional attacks. The attack surface includes not only traditional SSRF targets like internal APIs but also cloud provider metadata services that often contain sensitive credentials or configuration data.
This vulnerability aligns with common security patterns identified in the CWE database under CWE-918, which specifically addresses server-side request forgery vulnerabilities where applications fail to properly validate user-provided URLs before using them in HTTP requests. The issue also intersects with ATT&CK framework techniques such as T1566.002 for phishing with social engineering and T1071.004 for application layer protocol usage, as attackers could potentially use this flaw to gain information about internal infrastructure or escalate privileges through access to sensitive metadata services. The vulnerability's exploitation requires only workspace user privileges, making it particularly concerning as it can be leveraged by individuals with relatively low-privilege access within the Typebot environment.
The remediation implemented in version 3.17.0 addresses this vulnerability by ensuring that all webhook forwarding operations utilize the repository's dedicated SSRF-protected `safeKy` client instead of the generic `ky` instance. This change enforces proper URL validation and network restriction mechanisms that prevent outbound requests to internal or localhost addresses, effectively closing the attack vector. The fix demonstrates the importance of maintaining consistent security practices throughout application codebases and highlights the critical need for dedicated security clients or middleware that can properly validate and sanitize user-controllable inputs before they are used in network operations. Organizations using Typebot should immediately upgrade to version 3.17.0 or later to mitigate this risk, while also implementing monitoring for any unauthorized webhook configuration changes that might indicate potential exploitation attempts.