CVE-2026-39969: CWE-287: Improper Authentication in baptisteArno typebot.io
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.
AI Analysis
Technical Summary
In TypeBot versions prior to 3.17.0, the WhatsApp Cloud API webhook endpoint (POST /v1/workspaces/{workspaceId}/whatsapp/{credentialsId}/webhook) fails to verify the x-hub-signature-256 HMAC signature provided by Meta on webhook deliveries. The webhook URL includes workspaceId and credentialsId as path parameters, which are exposed in logs and dashboards. This lack of verification allows unauthenticated attackers to spoof webhook messages, potentially triggering bot workflows and causing unauthorized interactions with external services under the workspace owner's credentials. The issue is addressed in version 3.17.0.
Potential Impact
An attacker can send spoofed webhook requests without authentication, leading to unauthorized triggering of bot flows and interaction with external services using the workspace owner's credentials. This may result in unauthorized actions and resource consumption. The confidentiality and integrity of the webhook-triggered processes are impacted, but availability is not directly affected. The CVSS score is 6.5 (medium severity).
Mitigation Recommendations
Upgrade TypeBot to version 3.17.0 or later, where the webhook endpoint properly verifies the x-hub-signature-256 HMAC signature. This official fix prevents unauthenticated spoofed webhook messages. Until upgraded, restrict access to the webhook endpoint if possible and monitor for suspicious activity, but the primary remediation is to apply the official patch.
CVE-2026-39969: CWE-287: Improper Authentication in baptisteArno typebot.io
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In TypeBot versions prior to 3.17.0, the WhatsApp Cloud API webhook endpoint (POST /v1/workspaces/{workspaceId}/whatsapp/{credentialsId}/webhook) fails to verify the x-hub-signature-256 HMAC signature provided by Meta on webhook deliveries. The webhook URL includes workspaceId and credentialsId as path parameters, which are exposed in logs and dashboards. This lack of verification allows unauthenticated attackers to spoof webhook messages, potentially triggering bot workflows and causing unauthorized interactions with external services under the workspace owner's credentials. The issue is addressed in version 3.17.0.
Potential Impact
An attacker can send spoofed webhook requests without authentication, leading to unauthorized triggering of bot flows and interaction with external services using the workspace owner's credentials. This may result in unauthorized actions and resource consumption. The confidentiality and integrity of the webhook-triggered processes are impacted, but availability is not directly affected. The CVSS score is 6.5 (medium severity).
Mitigation Recommendations
Upgrade TypeBot to version 3.17.0 or later, where the webhook endpoint properly verifies the x-hub-signature-256 HMAC signature. This official fix prevents unauthenticated spoofed webhook messages. Until upgraded, restrict access to the webhook endpoint if possible and monitor for suspicious activity, but the primary remediation is to apply the official patch.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-08T00:01:47.627Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a10ab40e1370fbb483c5075
Added to database: 5/22/2026, 7:15:12 PM
Last enriched: 5/22/2026, 7:15:48 PM
Last updated: 5/23/2026, 7:57:10 PM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.