PatchSiren cyber security CVE debrief
CVE-2026-96388 Drupal CVE debrief
A Cross-Site Request Forgery (CSRF) vulnerability exists in the Tawk.to - Live chat application for Drupal, affecting versions from 0.0.0 to 3.0.4. This issue allows attackers to perform actions on behalf of users without their consent. The vulnerability can lead to unauthorized actions being performed, potentially resulting in security breaches. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential CSRF attacks. It is essential to review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Additionally, defenders should implement CSRF protections and validate user requests to and
- Vendor
- Drupal
- Product
- Tawk.to - Live chat application
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-22
- Original CVE updated
- 2026-10-22
- Advisory published
- 2026-10-22
- Advisory updated
- 2026-10-22
Who should care
Drupal administrators and users of the Tawk.to - Live chat application should assess their exposure and take necessary actions to prevent potential CSRF attacks.
Why it matters
A Cross-Site Request Forgery (CSRF) vulnerability exists in the Tawk.to - Live chat application for Drupal, affecting versions from 0.0.0 to 3.0.4. This issue allows attackers to perform actions on behalf of users without their consent. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential CSRF attacks.
- Defenders should verify exposure and apply patches or mitigations to prevent potential CSRF attacks.
- CSRF attacks could allow attackers to perform actions on behalf of users without their consent.
- Defenders should implement CSRF protections and validate user requests to prevent potential attacks.
- Additional information on potential exploitation or impact is limited, and further verification is required.
Technical summary
The Tawk.to - Live chat application for Drupal is vulnerable to Cross-Site Request Forgery (CSRF) attacks. This issue affects versions from 0.0.0 to 3.0.4. An attacker could exploit this vulnerability to perform actions on behalf of users without their consent.
Defensive priority
Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential CSRF attacks.
Recommended defensive actions
- Verify the version of Tawk.to - Live chat application in use and assess exposure.
- Apply patches or updates to affected versions (from 0.0.0 to 3.0.4) as available.
- Implement CSRF protections and validate user requests to prevent potential attacks.
Evidence notes
The CVE record and source item provide details on the CSRF vulnerability in Tawk.to - Live chat application. However, additional information on potential exploitation or impact is limited.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-96388 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-96388
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-96388 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-96388
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Tawk.to - Live chat application - Critical - Cross Site Request Forgery - SA-CONTRIB-2026-184
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/96xxx/CVE-2026-96388.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://www.drupal.org/sa-contrib-2026-184
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.