- Package
- drupal/cookiecuttr
- Fixed in
- 2.0.3
- Published
- Wed 23 Sep 2026, 18:08 LisbonUpdated Mon 26 Oct 2026, 02:26 Lisbon
In plain words
An attacker with the administer cookiecuttr permission could store malicious values through the Cookiecuttr administration form. When those values are later displayed without adequate filtering, they could run scripts in a viewer's browser, causing stored cross-site scripting (XSS).
Am I affected?
Look for drupal/cookiecuttr and its version in composer.lock. The advisory lists 2.0.3 as fixed but gives no affected version range. Review which roles have the administer cookiecuttr permission, as an attacker needs that permission to submit values through the administration form.
What to do
Check which version you have, then update to a fixed release for your branch (2.0.3):
composer show drupal/cookiecuttr | grep versions
composer update drupal/cookiecuttr
If your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.
If you cannot update yet
The vulnerability is mitigated by the requirement that an attacker have a role with the administer cookiecuttr permission.
The advisory's description
This module enables you to provide information and options about cookie usage.
The module does not sufficiently filter input submitted through the Cookiecuttr administration form. This could allow specially crafted values to be stored and later rendered without adequate sanitization, resulting in a cross-site scripting (XSS) vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission administer cookiecuttr.
The advisory
- OSV.dev: DRUPAL-CONTRIB-2026-181
- The week's digest, with the other advisories from 21 Sep 2026
- All advisories for drupal/cookiecuttr