Vulnerability from drupal
Published
2025-04-23 16:59
Modified
2025-04-23 16:59
Summary
Details

Block Class enables you to add custom attributes to blocks.

The module did not sufficiently sanitize custom attribute input, allowing for potential XSS attacks when malicious JavaScript was injected as a custom attribute.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer block classes".

Credits
Ivo Van Geertruyen (mr.baileys) www.drupal.org/u/mrbaileys
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "affected_versions": "\u003e=4.0.0 \u003c4.0.1"
      },
      "package": {
        "ecosystem": "Packagist:https://packages.drupal.org/8",
        "name": "drupal/block_class"
      },
      "ranges": [
        {
          "database_specific": {
            "constraint": "\u003e=4.0.0 \u003c4.0.1"
          },
          "events": [
            {
              "introduced": "4.0.0"
            },
            {
              "fixed": "4.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "severity": []
    }
  ],
  "aliases": [
    "CVE-2025-3902"
  ],
  "credits": [
    {
      "contact": [
        "https://www.drupal.org/u/mrbaileys"
      ],
      "name": "Ivo  Van Geertruyen (mr.baileys)"
    }
  ],
  "details": "Block Class enables you to add custom attributes to blocks.\n\nThe module did not sufficiently sanitize custom attribute input, allowing for potential XSS attacks when malicious JavaScript was injected as a custom attribute.\n\nThis vulnerability is mitigated by the fact that an attacker must have a role with the permission \"administer block classes\".",
  "id": "DRUPAL-CONTRIB-2025-043",
  "modified": "2025-04-23T16:59:01.000Z",
  "published": "2025-04-23T16:59:01.000Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2025-043"
    }
  ],
  "schema_version": "1.7.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.