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

CVE-2026-55665

HIGH · 8.5 CVSS v4.0 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable No privileges Patch available 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
Grist is spreadsheet software using Python as its formula language. Prior to 1.7.15, Grist contained two cross-site scripting vulnerabilities where an attacker-controlled value reached a link's href without scheme validation, so a javascript URL could run in a victim's Grist origin on a single click. On the account-selection page, /welcome/select-account used its next query parameter as the account buttons' link target. In document tours, the GristDocTour table's Link_URL column became a clickable button, allowing an editor of a shared document to store a javascript URL there that ran when another user opened the document and clicked the tour link. Because the script runs in the victim's authenticated session, it can call Grist APIs as the victim, reading or modifying data and changing sharing settings and access rules. A document editor could therefore escalate to owner-level access. This issue is fixed in version 1.7.15.

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

Grist contained two XSS vulnerabilities allowing javascript: URL injection. First, the /welcome/select-account page used the 'next' query parameter as account button link targets without scheme validation, permitting javascript: URLs. Second, in document tours, the GristDocTour table's Link_URL column became clickable, letting document editors embed javascript: URLs that execute when users open the document and click the tour link. Both run in the victim's authenticated session.

MitigationUpgrade Grist to version 1.7.15 or later to patch both XSS vulnerabilities. Review document tours and shared documents for any malicious Link_URL entries.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Check installed Grist version
    Run 'pip show grist' or inspect package.json for the grist package version, or access Grist UI and check the version in the help/about section
    Affected if Version is below 1.7.15 - both vulnerabilities exist in prior versions
  2. Verify document tours feature access
    Check if any user has Editor or Owner access to a workspace containing a GristDocTour table, or check database for presence of GristDocTour tables with populated Link_URL columns
    Affected if Document tours are in use and Link_URL column contains javascript: or other non-http(s) URLs - stored XSS is possible
  3. Inspect /welcome/select-account endpoint behavior
    Access the account selection page and observe if the 'next' query parameter is reflected as a clickable link without scheme validation in the HTML output
    Affected if The 'next' parameter allows javascript: URLs to be rendered as clickable links - XSS is possible

You are affected if running Grist version below 1.7.15 and either document tours are enabled with GristDocTour tables present or users access the account-selection page with untrusted 'next' parameters.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Grist to version 1.7.15 or later to patch both XSS vulnerabilities. Review document tours and shared documents for any malicious Link_URL entries.

Recommended fix High confidence

1.7.15

  1. 1. Identify current Grist version by checking the running container or package.json/version file
  2. 2. If version is prior to 1.7.15, plan for upgrade to version 1.7.15 or later
  3. 3. Backup all Grist data and document databases before upgrading
  4. 4. Stop the Grist service
  5. 5. Update Grist to version 1.7.15 using the installation method in use (e.g., Docker pull gristlabs/grist-core:1.7.15, pip upgrade, or npm update)
  6. 6. Verify the upgrade completed successfully by checking the version number after restart
  7. 7. Confirm the /welcome/select-account page now properly validates the 'next' query parameter
  8. 8. Confirm document tour Link_URL column no longer executes javascript: URLs
Caveat Minor version upgrade; review release notes for any configuration or data migration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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