Description

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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.4",
  "pubDate": "2026-08-11T17:18:02.067Z",
  "pubdate": "2026-08-11T17:18:02.067Z",
  "executiveSummary": "A Server-Side Request Forgery (SSRF) vulnerability exists in Typebot prior to version 3.17.0 within the WhatsApp status forwarding feature.\nThe vulnerability allows an authenticated workspace user with permission to configure WhatsApp settings to supply arbitrary URLs, which the Typebot server subsequently requests.\nImpact includes the ability to make the server issue HTTP requests to internal services, private-network hosts, localhost, or cloud metadata-style endpoints.\nThis occurs because the application uses a raw `ky` instance instead of the repository's SSRF-protected `safeKy` client when forwarding WhatsApp marketing and error status events.\nExploitation requires workspace user privileges capable of configuring WhatsApp settings and a trigger mechanism where the public WhatsApp production webhook receives a status payload to be forwarded.",
  "technicalDetails": "The root cause of the vulnerability is the improper validation and insecure usage of HTTP client libraries within the WhatsApp status forwarding feature.\nPrior to version 3.17.0, the workspace-configured webhook forwarding URL is only validated as a generic URL within the application settings.\nWhen processing and forwarding WhatsApp marketing or error status events, the server-side code uses the raw `ky` HTTP client instance rather than utilizing the repository's dedicated SSRF-protected `safeKy` client.\nThe attack flow proceeds as follows: First, an authenticated attacker with workspace user privileges modifies the WhatsApp configuration settings to include a malicious URL pointing to an internal service, private-network host, localhost, or a cloud provider metadata endpoint.\nSecond, the public WhatsApp production webhook receives an external status payload that triggers the forwarding mechanism.\nThird, upon receiving this status payload, the Typebot server initiates an outbound HTTP POST request via the raw `ky` instance to the stored URL provided by the user.\nBecause the raw `ky` client lacks network-level restrictions and SSRF defenses, the server successfully queries internal resources that are normally inaccessible from external networks.\nPrivilege requirements are limited to workspace user access capable of configuring WhatsApp settings, and the affected component is the WhatsApp status forwarding logic in Typebot versions prior to 3.17.0."
}