dbcve.org
Google Analytics Ga4Drupal extension · Sujanshrestha

CVE-2026-3529

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 1.1.14 or later.
See remediation →
68/100
Remediation priority · Elevated
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 Google Analytics GA4 allows Cross-Site Scripting (XSS).This issue affects Google Analytics GA4: from 0.0.0 before 1.1.14.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in the Drupal Google Analytics GA4 module. The vulnerability stems from improper neutralization of user input during web page generation, allowing attackers to inject malicious JavaScript code that executes when other users view affected pages.

MitigationUpdate the Google Analytics GA4 module to version 1.1.14 or later to obtain the patched version that properly sanitizes input.

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 Analytics Ga4Drupal extension
Affected:< 1.1.14

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Google Analytics GA4 module is installed
    Check your Drupal installation for the presence of the Google Analytics GA4 module (typically in modules/contrib or modules directory)
    Affected if The module directory exists in the Drupal modules folder
  2. Check installed module version
    Locate the module's info.yml or composer.json file and read the version number
    Affected if The version is below 1.1.14 (e.g., 1.1.13, 1.1.12, etc.)
  3. Confirm module is enabled
    Check Drupal's module administration interface or database for enabled module status
    Affected if The module is both installed and enabled in the Drupal site
  4. Identify user input points in the module
    Review the module's form handlers and content creation interfaces where user-supplied data is processed and displayed
    Affected if The module accepts user input that gets rendered without sanitization

You are affected if the Google Analytics GA4 module is installed, enabled, and running a version lower than 1.1.14.

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.1.14 or later
Fixed in 1.1.14
Interim mitigation

Update the Google Analytics GA4 module to version 1.1.14 or later to obtain the patched version that properly sanitizes input.

Recommended fix High confidence

1.1.14

  1. 1. Back up your Drupal site database and files before making any changes.
  2. 2. Navigate to your Drupal administration dashboard.
  3. 3. Go to Extend (or Modules) page.
  4. 4. Locate the 'Google Analytics GA4' module in the list.
  5. 5. Check for available updates for the module.
  6. 6. If using Composer for Drupal dependency management, run: composer update drupal/google_analytics_ga4 --with-all-dependencies
  7. 7. Alternatively, download version 1.1.14 from Drupal.org and install via the Update manager or manually replace the module files.
  8. 8. Clear Drupal caches after upgrading: drush cr all or via admin UI at Configuration > Development > Performance > Clear all caches.

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

Fix this in Google Analytics Ga4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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