dbcve.org
Siteimprove AnalyticsDrupal extension · Ijsbrandy

CVE-2026-15082

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 2.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 6 weeks old

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 Siteimprove Analytics allows Cross-Site Scripting (XSS). This issue affects Siteimprove Analytics versions: from 0.0.0 to 2.0.1.

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 · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in Drupal Siteimprove Analytics module (versions 0.0.0 to 2.0.1) due to improper neutralization of user-supplied input during web page generation. Attackers can inject malicious JavaScript that executes in the browsers of users viewing affected content.

MitigationUpdate Siteimprove Analytics to the latest patched version once released, or implement output encoding/sanitization on all user-supplied data handled by the module. Disable the module if no patch is available.

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
Siteimprove AnalyticsDrupal extension
Affected:< 2.0.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 Siteimprove Analytics module is installed
    In the Drupal admin interface, navigate to Extend or Modules (depending on Drupal version). Search for 'Siteimprove Analytics' in the list of installed modules. Alternatively, check the modules directory for a folder named 'siteimprove_analytics'.
    Affected if The module appears in the list of installed modules and is enabled
  2. Determine the installed module version
    In Drupal admin, go to Extend > Siteimprove Analytics > Version column. Alternatively, check the siteimprove_analytics.info.yml file in the module directory for the 'version' entry.
    Affected if The version listed is 2.0.1 or lower (0.0.0 through 2.0.1 are affected)
  3. Confirm the module is actively processing content
    Check if the Siteimprove Analytics module is enabled and configured to track content. Look at the module configuration page at /admin/config/content/siteimprove or inspect whether the module is hooked into page rendering.
    Affected if The module is enabled and actively processing or rendering web pages with Siteimprove tracking code
  4. Identify if user-supplied input reaches the module
    Review which content types and fields the Siteimprove Analytics module is tracking. Check if the module is set to analyze content that includes user-generated input such as comments, node titles, body content, or custom fields.
    Affected if The module is configured to track content containing user-supplied data without additional sanitization

The environment is affected if the Siteimprove Analytics module is installed and enabled with a version between 0.0.0 and 2.0.1, and it processes any user-supplied content that could contain malicious scripts.

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.

From vendor data
Upgrade available Upgrade to 2.0.1 or later
Fixed in 2.0.1
Interim mitigation

Update Siteimprove Analytics to the latest patched version once released, or implement output encoding/sanitization on all user-supplied data handled by the module. Disable the module if no patch is available.

Fix this in Siteimprove Analytics Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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