dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-45806

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A cross-site scripting (XSS) vulnerability in rrweb-snapshot before v2.0.0-alpha.18 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.

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

Cross-site scripting (XSS) vulnerability in rrweb-snapshot library versions prior to v2.0.0-alpha.18 allows execution of arbitrary web scripts or HTML through a crafted payload, likely during the snapshot/recording process.

MitigationUpgrade rrweb-snapshot to v2.0.0-alpha.18 or later. Additionally, implement Content Security Policy (CSP) headers and validate/sanitize any untrusted input before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Identify rrweb-snapshot version
    Run 'npm list rrweb-snapshot' or inspect package.json dependencies to determine the installed version of rrweb-snapshot
    Affected if Version is present and is earlier than v2.0.0-alpha.18
  2. Check transitive dependencies
    Search package-lock.json for 'rrweb-snapshot' entries and note the resolved version across all dependency trees
    Affected if Any resolved version is earlier than v2.0.0-alpha.18
  3. Verify if snapshot recording is in use
    Review application code to determine if rrweb-snapshot is invoked to capture or serialize DOM content, user inputs, or page state
    Affected if The application uses rrweb-snapshot to process any user-supplied or untrusted HTML content
  4. Inspect snapshot endpoint configuration
    Check application configuration and network requests to identify endpoints that receive snapshot data (often /__rrweb__, /recording, or similar paths)
    Affected if Snapshot endpoints accept payloads that could contain unsanitized HTML or script content

Environment is affected if rrweb-snapshot version is earlier than v2.0.0-alpha.18 AND the application processes untrusted content through the snapshot or recording functionality

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade rrweb-snapshot to v2.0.0-alpha.18 or later. Additionally, implement Content Security Policy (CSP) headers and validate/sanitize any untrusted input before processing.

Recommended fix Moderate confidence

rrweb-snapshot v2.0.0-alpha.18 or later

  1. Identify the rrweb-snapshot package in your project dependencies
  2. Update rrweb-snapshot to version v2.0.0-alpha.18 or later using your package manager (e.g., npm install [email protected] or later)
  3. Verify the update was successful by checking the installed version
  4. Rebuild and test your application to ensure the XSS vulnerability is remediated
Caveat Alpha releases may have unstable APIs; review changelog before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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