dbcve.org
Google TagDrupal extension · Google Tag Project

CVE-2025-31683

MEDIUM · 6.8 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.0.8 / 8.x-1.8 or later.
See remediation →
75/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
Cross-Site Request Forgery (CSRF) vulnerability in Drupal Google Tag allows Cross Site Request Forgery.This issue affects Google Tag: from 0.0.0 before 1.8.0, from 2.0.0 before 2.0.8.

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 Request Forgery (CSRF) vulnerability in the Drupal Google Tag module allows attackers to trick authenticated users into performing unwanted actions (such as modifying Google Tag Manager configuration) by leveraging the lack of anti-CSRF token validation on module forms.

MitigationUpdate Drupal Google Tag module to version 1.8.0 or 2.0.8 or later, which includes anti-CSRF token protection for affected forms.

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
Google TagDrupal extension
Affected:>= 7.x-1.0, < 8.x-1.8>= 2.0.0, < 2.0.8

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Identify installed Google Tag module version
    Navigate to Drupal admin panel at /admin/modules or run `drush pm-list --status=enabled --type=module` to list enabled modules. Locate the 'Google Tag' module and note its version number.
    Affected if The version is 7.x-1.0 through 7.x-1.7, or 2.0.0 through 2.0.7
  2. Verify the module is enabled
    Confirm the Google Tag module status shows as 'Enabled' in the modules list at /admin/modules, or check the system table for the module entry with status=1.
    Affected if The module is installed and enabled, making the CSRF-protected forms accessible to authenticated users
  3. Check if configuration forms are accessible
    Navigate to the Google Tag configuration page at /admin/config/system/google-tag or use drush to confirm the route is available: `drush routing | grep google_tag`.
    Affected if Configuration forms for Google Tag Manager are accessible without token validation on vulnerable versions

You are affected if the Google Tag module is enabled and its installed version falls within 7.x-1.0 to 7.x-1.7 or 2.0.0 to 2.0.7, lacking anti-CSRF token protection on its forms.

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 2.0.8 / 8.x-1.8 or later
Fixed in 2.0.88.x-1.8
Interim mitigation

Update Drupal Google Tag module to version 1.8.0 or 2.0.8 or later, which includes anti-CSRF token protection for affected forms.

Recommended fix High confidence

8.x-1.8 for 7.x branch; 2.0.8 for 2.x branch

  1. 1. Back up your Drupal site database and files before proceeding with any updates.
  2. 2. Identify which branch of the Google Tag module is installed (7.x or 2.x) by checking your codebase or Drupal administration interface.
  3. 3. If using 7.x version branch (versions 7.x-1.0 through 7.x-1.7): upgrade to 8.x-1.8 or later.
  4. 4. If using 2.x version branch (versions 2.0.0 through 2.0.7): upgrade to 2.0.8 or later.
  5. 5. Update the module using Composer (composer update drupal/google_tag) or via Drupal's administration interface.
  6. 6. Clear Drupal caches after the upgrade to ensure the new version is fully loaded.
  7. 7. Verify that Google Tag functionality continues to work correctly by testing tag firing on your site.
Caveat Review the module's release notes for any configuration or compatibility changes between your current version and the fixed release

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

Fix this in Google Tag Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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