dbcve.org
BotpressApplication

CVE-2026-4984

HIGH · 8.2 CVSS v3.1 Published 2026-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
The Twilio integration webhook handler accepts any POST request without validating Twilio's 'X-Twilio-Signature'. When processing media messages, it fetches user-controlled URLs ('MediaUrlN' parameters) using HTTP requests that include the integration's Twilio credentials in the 'Authorization' header. An attacker can forge a webhook payload pointing to their own server and receive the victim's 'accountSID' and 'authToken' in plaintext (base64-encoded Basic Auth), leading to full compromise of the Twilio account.

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 Twilio integration webhook handler fails to validate the X-Twilio-Signature header, allowing attackers to forge arbitrary webhook payloads. When processing media messages, the handler fetches user-controlled MediaUrlN parameters and includes the integration's Twilio credentials (accountSID and authToken) as base64-encoded Basic Auth in the Authorization header. Attackers can craft malicious webhook payloads pointing to their controlled server to intercept and exfiltrate these plaintext credentials, achieving full account compromise.

MitigationImplement X-Twilio-Signature header validation on all incoming webhook requests using Twilio's documented algorithm, and avoid sending credentials to user-controlled URLs or implement additional safeguards such as URL allow-listing.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BotpressApplication
Affected:all versions

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
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Twilio integration in your environment
    Search your codebase, configuration files, or environment variables for Twilio credentials (accountSID, authToken) or Twilio-related webhook endpoint configurations
    Affected if You have Twilio integration configured with stored credentials and webhooks enabled
  2. Locate webhook handler code
    Search for webhook endpoint handlers that process incoming requests from Twilio, particularly those handling media messages or MediaUrlN parameters
    Affected if Your application has Twilio webhook handlers that process media messages without signature validation
  3. Check for X-Twilio-Signature validation
    Inspect your webhook handler code to verify if it validates the X-Twilio-Signature header using Twilio's documented validation algorithm before processing requests
    Affected if The webhook handler does not validate or incorrectly validates the X-Twilio-Signature header
  4. Inspect credential handling in media processing
    Examine how MediaUrlN parameters from webhook payloads are processed and whether Twilio credentials are included in requests to those URLs
    Affected if The handler sends base64-encoded Basic Auth credentials (accountSID:authToken) in the Authorization header when fetching user-controlled MediaUrlN URLs

You are affected if you have a Twilio integration with webhooks that process media messages without validating the X-Twilio-Signature header, allowing attacker-controlled URLs to receive your Twilio credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement X-Twilio-Signature header validation on all incoming webhook requests using Twilio's documented algorithm, and avoid sending credentials to user-controlled URLs or implement additional safeguards such as URL allow-listing.

Fix this in Botpress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4984 — 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-4984 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