dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-39969

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WhatsApp Cloud API webhook endpoint in TypeBot versions 3.16.0 and prior fails to verify the x-hub-signature-256 HMAC signature that Meta includes with every webhook delivery. Additionally, the exposed workspaceId and credentialsId path parameters are logged in access logs and visible in Meta's webhook dashboard, enabling unauthenticated attackers to send spoofed webhook messages.

MitigationUpgrade to TypeBot version 3.17.0 or later which implements proper HMAC signature verification. Until upgraded, consider restricting webhook endpoint access via additional authentication layers or network-level controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TypeBot version
    Check the TypeBot application version through its admin UI, docker container label, package.json, or API endpoint /api/version. Compare against the fixed version 3.17.0.
    Affected if The installed version is below 3.17.0 and the application uses WhatsApp Cloud API integration.
  2. Verify WhatsApp Cloud API webhook integration exists
    Confirm that a WhatsApp Cloud API integration is configured in TypeBot by reviewing the workspace integrations settings or checking for WhatsApp-related environment variables/webhook configurations.
    Affected if WhatsApp Cloud API integration is enabled and exposes a public webhook endpoint.
  3. Test webhook signature validation
    Send a test POST request to the WhatsApp webhook endpoint (typically /webhooks/whatsapp) with a forged or missing x-hub-signature-256 header. Observe whether the request is rejected or accepted.
    Affected if The webhook accepts requests without a valid HMAC signature or rejects requests with an invalid signature.
  4. Inspect for exposed workspaceId and credentialsId
    Review TypeBot server logs and the Meta for Developers dashboard (Webhooks section) for any logged path parameters containing workspaceId or credentialsId values.
    Affected if Sensitive identifiers are visible in logs or Meta's webhook configuration interface.
  5. Check HMAC verification configuration
    Examine the TypeBot configuration files, environment settings, or webhook settings to determine whether HMAC signature verification is enabled for incoming WhatsApp requests.
    Affected if HMAC signature verification is disabled or not configured for the WhatsApp webhook.

A user is affected if their TypeBot version is below 3.17.0, WhatsApp Cloud API integration is active, and the webhook endpoint accepts requests without validating the x-hub-signature-256 header.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to TypeBot version 3.17.0 or later which implements proper HMAC signature verification. Until upgraded, consider restricting webhook endpoint access via additional authentication layers or network-level controls.

Recommended fix High confidence

3.17.0

  1. Backup your current TypeBot installation and database before upgrading
  2. Upgrade TypeBot to version 3.17.0
  3. Verify the upgrade was successful by checking the application version
  4. Confirm that the WhatsApp Cloud API webhook endpoint now validates the x-hub-signature-256 HMAC signature
  5. Test the webhook functionality to ensure legitimate Meta webhooks are processed correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39969 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39969 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data