dbcve.org
Cookies Consent ManagementDrupal extension · Cookies Consent Management Project

CVE-2025-8092

HIGH · 7.6 CVSS v3.1 Published 2025-08-15
Fix available
A fix is available. Upgrade to 1.2.16 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges

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.16.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in the Drupal COOKiES Consent Management module. The vulnerability stems from improper input neutralization, allowing an attacker to inject malicious JavaScript code through the consent management interface. This injected script executes when other users view pages rendering the consent banner or related output.

MitigationUpgrade the COOKiES Consent Management module to version 1.2.16 or later. Review all consent-related form inputs and output contexts for proper sanitization and encoding.

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.16

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify COOKiES Consent Management module is installed
    Check the Drupal modules directory for the cookies_consent folder, typically located at modules/contrib/cookies_consent or modules/cookies_consent. Also check the Drupal admin interface at Extend (admin/modules) for the COOKiES Consent Management module.
    Affected if The module is present in the codebase or enabled in Drupal
  2. Determine installed module version
    Locate the .info.yml file in the cookies_consent module directory (modules/contrib/cookies_consent/cookies_consent.info.yml or similar path) and read the 'version' or 'core' and 'version' fields. Alternatively, check composer.json if installed via Composer.
    Affected if Version is less than 1.2.16 or version field is absent/unknown and the module is installed
  3. Confirm consent management functionality is accessible
    Log into Drupal admin panel and navigate to the COOKiES Consent Management configuration section, typically under Configuration > COOKiES Consent or similar path in the admin menu. Check if the consent banner configuration forms are accessible.
    Affected if The consent management interface is accessible and the module is enabled with consent functionality configured
  4. Verify consent banner output is rendered on site pages
    Visit the public-facing pages of the Drupal site and inspect whether a consent banner, cookie notice, or COOKiES-related UI element is displayed. Check page source (View > Developer > View Source) for elements with IDs/classes related to cookie consent (e.g., cookies-banner, cookie-notice).
    Affected if Consent banner or cookie-related UI elements are rendered on site pages, allowing injected scripts to execute when users visit the site

Your environment is affected if the COOKiES Consent Management module version is below 1.2.16 AND the module is enabled with the consent banner configured to display on site pages.

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.16 or later
Fixed in 1.2.16
Interim mitigation

Upgrade the COOKiES Consent Management module to version 1.2.16 or later. Review all consent-related form inputs and output contexts for proper sanitization and encoding.

Recommended fix High confidence

1.2.16

  1. Back up your Drupal site (database and files) before proceeding with any updates
  2. Navigate to your Drupal admin panel and go to Extend > Modules
  3. Locate the 'COOKiES Consent Management' module and verify the current version number
  4. Update the module using one of these methods: a) Run 'composer update drupal/cookies_consent_management --with-all-dependencies' in your terminal, b) Use Drush with 'drush up cookies_consent_management', or c) Download version 1.2.16 from www.drupal.org and install manually via the Extend page
  5. Clear the Drupal cache after the update (via admin UI at Configuration > Development > Performance > Clear all caches, or using 'drush cr')
  6. Verify the installed version shows 1.2.16 or later in the Extend modules list

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8092 — 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-8092 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