dbcve.org
Cookies Consent ManagementDrupal extension · Drupal

CVE-2025-48915

HIGH · 8.6 CVSS v3.1 Published 2025-06-13
Fix available
A fix is available. Upgrade to 1.2.15 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal COOKiES Consent Management allows Cross-Site Scripting (XSS).This issue affects COOKiES Consent Management: from 0.0.0 before 1.2.15.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in the Drupal COOKiES Consent Management module allows attackers to inject malicious scripts into web pages through improper input handling. This affects versions prior to 1.2.15. The vulnerability stems from insufficient input sanitization during web page generation.

MitigationUpgrade the COOKiES Consent Management module to version 1.2.15 or later to remediate the XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cookies Consent ManagementDrupal extension
Affected:< 1.2.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the module version file
    Find the COOKiES Consent Management module directory in your Drupal installation (typically in modules/contrib/ or modules/custom/) and open the cookies_consent.info.yml or cookies_consent.module file to read the version number
    Affected if The version listed is below 1.2.15 (for example, 1.2.14, 1.2.10, 1.1.x, etc.)
  2. Check module version via Composer
    If the module was installed via Composer, run 'composer show drupal/cookies_consent' or check your composer.lock file for the installed version of the cookies_consent package
    Affected if The installed version shown is lower than 1.2.15
  3. Verify module is enabled
    Log into Drupal admin panel and navigate to Extend (or modules list) to confirm the COOKiES Consent Management module is installed and enabled on your site
    Affected if The module is enabled and the version from steps 1 or 2 is below 1.2.15

Your environment is affected if the COOKiES Consent Management module is enabled and its installed version is anything less than 1.2.15, as this is the version that contains the fix for the XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.15 or later
Fixed in 1.2.15
Interim mitigation

Upgrade the COOKiES Consent Management module to version 1.2.15 or later to remediate the XSS vulnerability.

Recommended fix High confidence

1.2.15

  1. Backup your Drupal database and files before proceeding
  2. Put your Drupal site into maintenance mode via Administration > Configuration > Development > Maintenance mode
  3. Download the COOKiES Consent Management module version 1.2.15 from www.drupal.org/project/cookies
  4. Navigate to the Drupal modules directory (typically /modules or /modules/contrib)
  5. Remove or rename the existing cookies directory
  6. Extract the new version 1.2.15 to the modules directory
  7. Run database updates if required: drush updatedb or navigate to /update.php
  8. Clear all Drupal caches: drush cache-rebuild or via Administration > Configuration > Development > Performance > Clear all caches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cookies Consent Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48915 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data