FKIE_CVE-2026-4984

Vulnerability from fkie_nvd - Published: 2026-03-27 15:17 - Updated: 2026-03-30 13:26
Severity ?
8.2 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Summary
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.
References
vulnreport@tenable.comhttps://www.tenable.com/security/research/tra-2026-22
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The Twilio integration webhook handler accepts any POST request without validating Twilio\u0027s \u0027X-Twilio-Signature\u0027.\n\nWhen processing media messages, it fetches user-controlled URLs (\u0027MediaUrlN\u0027 parameters) using HTTP requests that include the integration\u0027s Twilio credentials in the \u0027Authorization\u0027 header.\n\nAn attacker can forge a webhook payload pointing to their own server and receive the victim\u0027s \u0027accountSID\u0027 and \u0027authToken\u0027 in plaintext (base64-encoded Basic Auth), leading to full compromise of the Twilio account."
    }
  ],
  "id": "CVE-2026-4984",
  "lastModified": "2026-03-30T13:26:29.793",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 8.2,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 4.2,
        "source": "vulnreport@tenable.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-03-27T15:17:03.953",
  "references": [
    {
      "source": "vulnreport@tenable.com",
      "url": "https://www.tenable.com/security/research/tra-2026-22"
    }
  ],
  "sourceIdentifier": "vulnreport@tenable.com",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.