TypeBot: WhatsApp Webhook Endpoint Missing Signature Verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| baptisteArno | typebot.io | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Baptistearno | Typebot.io |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.140% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Baptistearno
Baptistearno typebot.io |
|
| Vendors & Products |
Baptistearno
Baptistearno typebot.io |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | TypeBot is a chatbot builder tool. In versions 3.16.0 and prior, the WhatsApp Cloud API webhook endpoint (POST /v1/workspaces/{workspaceId}/whatsapp/{credentialsId}/webhook) does not verify the x-hub-signature-256 HMAC signature included by Meta in every webhook delivery. The webhook URL exposes both workspaceId and credentialsId as path parameters, which are logged in web server access logs, visible in Meta's webhook configuration dashboard, and potentially shared when configuring integrations. This allows any unauthenticated attacker to send spoofed webhook messages to trigger bot flows, consume API resources, and interact with external services using the workspace owner's credentials. The issue has been fixed in version 3.17.0. | |
| Title | TypeBot: WhatsApp Webhook Endpoint Missing Signature Verification | |
| Weaknesses | CWE-287 CWE-345 |
|
| References |
| |
| Metrics |
cvssV3_1
|