PatchSiren cyber security CVE debrief
CVE-2026-96379 Drupal CVE debrief
A Cross-site Scripting (XSS) vulnerability exists in Drupal's CookieCuttr module versions from 2.0.0 to 2.0.3. This issue allows for Stored XSS, which can be exploited if an attacker can inject malicious input that is not properly neutralized during web page generation. The vulnerability arises from improper neutralization of input during web page generation. Defenders should verify exposure of CookieCuttr versions 2.0.0 to 2.0.3 and assess the need for updates or mitigations. The CVE record and source item provide details on the vulnerability, but specific exploit details or attack vectors are not provided, limiting the ability to assess full impact. It is crucial to prioritize a
- Vendor
- Drupal
- Product
- CookieCuttr
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-22
- Original CVE updated
- 2026-10-30
- Advisory published
- 2026-10-22
- Advisory updated
- 2026-10-30
Who should care
Defenders responsible for Drupal installations using the CookieCuttr module, particularly those with user-supplied input that could be exploited for XSS, should assess exposure and prioritize remediation.
Why it matters
CVE-2026-96379 represents a Stored Cross-site Scripting (XSS) vulnerability in Drupal's CookieCuttr module versions 2.0.0 to 2.0.3. Defenders should verify exposure, enhance input validation, monitor for suspicious activity, and prioritize updates to mitigate potential risks.
- Verification of exposure for CookieCuttr versions 2.0.0 to 2.0.3 is necessary to prevent potential XSS attacks.
- Enhancement of input validation and sanitization can mitigate the risk of stored XSS.
- Monitoring for suspicious activity related to user-supplied input can help detect potential attacks.
- Prioritization of updates or mitigations for affected CookieCuttr versions is crucial for maintaining security.
Technical summary
The CookieCuttr module for Drupal is vulnerable to Stored Cross-site Scripting (XSS). The issue arises from improper neutralization of input during web page generation, affecting versions from 2.0.0 to 2.0.3. An attacker could potentially inject malicious scripts, although specific attack vectors are not detailed in the provided sources.
Defensive priority
Defenders should prioritize verifying exposure of CookieCuttr versions 2.0.0 to 2.0.3 and assess the need for updates or mitigations.
Recommended defensive actions
- Verify CookieCuttr version and update to 2.0.4 or later if possible.
- Review and enhance input validation and sanitization for user-supplied data in CookieCuttr.
- Monitor for suspicious activity related to stored XSS attacks.
Evidence notes
The CVE record and source item provide details on the vulnerability in CookieCuttr versions 2.0.0 to 2.0.3. However, specific exploit details or attack vectors are not provided, limiting the ability to assess full impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-96379 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-96379
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-96379 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-96379
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
CookieCuttr - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-181
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/96xxx/CVE-2026-96379.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://www.drupal.org/sa-contrib-2026-181
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.