Security readout for executives and security teams
Plain-English summary
Botpress's Twilio chat integration accepts unauthenticated webhook calls. An attacker can send a fake message that tricks Botpress into fetching an attacker-controlled URL while attaching the customer's Twilio username and password. The attacker captures those credentials and can then take over the Twilio account, send messages, place calls, and rack up charges in the victim's name.
Executive priority
Treat as a high-priority patch and credential-rotation task this sprint. The flaw enables full takeover of the Twilio account tied to your chatbot, which directly translates to fraud charges, brand-damaging smishing from your numbers, and potential regulatory exposure. Fix windows should be measured in days, not weeks, especially given published research details.
Technical view
The Twilio webhook handler does not verify the X-Twilio-Signature HMAC, so any unauthenticated POST is trusted. When the payload includes MediaUrlN parameters, the handler issues an outbound HTTP request to that URL using HTTP Basic Auth populated with the integration's accountSID and authToken. Forging a webhook with an attacker-hosted MediaUrl causes Botpress to leak base64-encoded Twilio credentials in the Authorization header (CWE-345, CWE-352).
Likely exposure
Any Botpress deployment with the Twilio integration enabled and a publicly reachable webhook endpoint is exposed. No authentication, user interaction, or prior access is required. Exposure scales with Twilio account privileges and balance: SMS, voice, WhatsApp, and Verify services can be abused for fraud, smishing, or toll fraud after credential capture.
Exploitation context
CVSS 8.2 (AV:N/AC:L/PR:N/UI:N) reflects a network-reachable, unauthenticated flaw. Tenable Research (TRA-2026-22) published technical details on 2026-03-27. The CVE is not currently listed in CISA KEV, and no public reports of in-the-wild exploitation have been cited in the source bundle. Public research disclosure, however, materially increases the likelihood of opportunistic abuse.
Researcher notes
Root cause is two-fold: missing webhook authenticity check (CWE-345) and credential reuse on outbound fetches to untrusted URLs. When validating remediation, confirm both that signature verification is enforced and that outbound MediaUrl fetches no longer attach Twilio Basic Auth to arbitrary hosts. Tenable's TRA-2026-22 is the authoritative technical reference; affected versions in the CVE record are sparse, so verify your deployed Botpress version against vendor advisories.
Mitigation direction
- Apply the Botpress Twilio integration update referenced in Tenable TRA-2026-22 and vendor advisories.
- Restrict the Twilio webhook endpoint to Twilio source IP ranges at the edge or WAF.
- Rotate any Twilio accountSID/authToken used by Botpress and revoke prior credentials.
- Enforce signature validation (X-Twilio-Signature) on all inbound Twilio webhooks.
- Scope Twilio API keys to least privilege and enable spending alerts in the Twilio console.
- If patching is delayed, disable the Twilio integration until validated mitigations are in place.
Validation and detection
- Inventory Botpress instances and confirm whether the Twilio integration is enabled.
- Review Twilio account usage logs for unexpected sends, calls, or geographies after 2026-03-27.
- Test the webhook endpoint to confirm signature validation rejects unsigned or invalid requests.
- Inspect Botpress outbound HTTP logs for requests to unfamiliar MediaUrl hosts.
- Confirm rotated Twilio credentials are in use and old tokens are revoked.
- Re-test post-patch using a benign signed payload to verify normal media handling still works.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-4984 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2tenableVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.tenable.com/security/research/tra-2026-22CVE reference, tenable
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.