Vulnerability from drupal – Published: 2026-11-11 18:02 – Updated: 2026-11-11 18:02 – Source website
This module enables you to manage user consent for external services, such as embedded videos. The COOKiES Video submodule blocks external video elements until the visitor accepts the consent banner, then re-enables them.
The module doesn't sufficiently check the value of the data-cookies-video-blazy-src attribute when it converts it back to a src attribute for Blazy iframes. The protocol check added in SA-CONTRIB-2025-092 covered the other conversion paths but missed this one.
This vulnerability is mitigated by the fact that an attacker must have the correct permissions to have a specific HTML element display for all users, and that element must have a specific class set.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.2.17"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/cookies"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.2.17"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.17"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [],
"credits": [
{
"contact": [
"https://www.drupal.org/u/whippet"
],
"name": "Whippet (VenusTech ADLab) (whippet)"
}
],
"details": "This module enables you to manage user consent for external services, such as embedded videos. The COOKiES Video submodule blocks external video elements until the visitor accepts the consent banner, then re-enables them.\n\nThe module doesn\u0027t sufficiently check the value of the `data-cookies-video-blazy-src` attribute when it converts it back to a `src` attribute for Blazy iframes. The protocol check added in [SA-CONTRIB-2025-092](https://www.drupal.org/sa-contrib-2025-092) covered the other conversion paths but missed this one.\n\nThis vulnerability is mitigated by the fact that an attacker must have the correct permissions to have a specific HTML element display for all users, and that element must have a specific class set.",
"id": "DRUPAL-CONTRIB-2026-334",
"modified": "2026-11-11T18:02:50.000Z",
"published": "2026-11-11T18:02:50.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-334"
}
],
"schema_version": "1.7.0"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.