{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-4984 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4984 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4984 is a high-severity vulnerability in botpress, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4984 and fix it if it is affected.\n\nWhat it is: CVE-2026-4984 is a high-severity vulnerability in botpress, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-4984 in the wild and no public exploit code.\n\nAffected product: botpress. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-4984/ (Markdown: https://insights.sbomify.com/CVE-2026-4984/index.md)","id":"CVE-2026-4984","markdown":"https://insights.sbomify.com/CVE-2026-4984/index.md","name":"CVE-2026-4984","record":{"aliases":["GHSA-6mjh-67rm-ph7x"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Botpress chatbot platform","requires_auth":"none","summary":"Attackers can steal Twilio credentials by forging webhook requests, leading to full compromise of the associated Twilio account.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"tenable","cpe":[{"product":"botpress","vendor":"botpress"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The Twilio integration webhook handler accepts any POST request without validating Twilio's 'X-Twilio-Signature'.\n\nWhen processing media messages, it fetches user-controlled URLs ('MediaUrlN' parameters) using HTTP requests that include the integration's Twilio credentials in the 'Authorization' header.\n\nAn 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Botpress - Credential Disclosure via Twilio Webhook Handler","id":"CVE-2026-4984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"dloebl CGIF GIF Image cgif.c cgif_addframe integer overflow","id":"CVE-2026-4985"},"packages":[],"prev":{"headline":"Cross-site scripting in Eclipse Open VSX","id":"CVE-2026-4983"},"products":["botpress"],"published":"2026-03-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-10","vendors":["botpress"]},"summary":"Attackers can steal Twilio credentials by forging webhook requests, leading to full compromise of the associated Twilio account.","url":"https://insights.sbomify.com/CVE-2026-4984/"}