CVE-2025-31682 — google_tag
MEDIUMCVE-2025-31682 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in drupal/google_tag. A fix is available for drupal/google_tag — see the affected versions and patch details below.
Google Tag - Moderately critical - Cross Site Scripting - SA-CONTRIB-2025-011
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-31682.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
drupal/google_tag🐘drupal/google_tagReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Google Tag allows Cross-Site Scripting (XSS). This issue affects Google Tag: from 0.0.0 before 1.8.0, from 2.0.0 before 2.0.8.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/google_tag | all versions | 1.8.0composer require drupal/google_tag:^1.8.0 |
| 🐘Packagist | drupal/google_tag | ≥ 2.0.0&&< 2.0.8 | 2.0.8composer require drupal/google_tag:^2.0.8 |
Affected Products
google taggoogle_tag_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/google_tag, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/google_tag to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31682 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2025-31682 in your dependencies?
Find it across Packagist, including transitive dependencies.