Vulnerability from drupal
Published
2025-05-28 17:43
Modified
2025-05-29 18:17
Summary
Details
The "Simple Klaro" module adds the "Klaro! A Simple Consent Manager" to your website and allows you to configure it according to your needs in the Drupal backend.
The module doesn't sufficiently mark its administrative permission as restricted, creating the possibility for the permission to be granted too broadly. A malicious admin could execute a Cross Site Scripting (XSS) attack.
This vulnerability is mitigated by the fact that an attacker must have a role with the "administer simple klaro" permission.
Credits
Pierre Rudloff (prudloff)
www.drupal.org/u/prudloff
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.10.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/simple_klaro"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.10.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.10.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2025-48918"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/prudloff"
],
"name": "Pierre Rudloff (prudloff)"
}
],
"details": "The \"Simple Klaro\" module adds the \"Klaro! A Simple Consent Manager\" to your website and allows you to configure it according to your needs in the Drupal backend.\n\nThe module doesn\u0027t sufficiently mark its administrative permission as restricted, creating the possibility for the permission to be granted too broadly. A malicious admin could execute a Cross Site Scripting (XSS) attack.\n\nThis vulnerability is mitigated by the fact that an attacker must have a role with the \"administer simple klaro\" permission.",
"id": "DRUPAL-CONTRIB-2025-071",
"modified": "2025-05-29T18:17:12.000Z",
"published": "2025-05-28T17:43:23.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2025-071"
}
],
"schema_version": "1.7.0"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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.
Loading…
Loading…