dbcve.org
Grist CoreApplication · Getgrist

CVE-2025-64753

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 1.7.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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-core is a spreadsheet hosting server. Prior to version 1.7.7, a user with only partial read access to a document could still access endpoints listing hashes for versions of that document and receive a full list of changes between versions, even if those changes contained cells, columns, or tables to which the user was not supposed to have read access. This was fixed in version 1.7.7 by restricting the `/compare` endpoint to users with full read access. As a workaround, remove sensitive document history using the `/states/remove` endpoint. Another possibility is to block the `/compare` endpoint.

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 an authorization bypass vulnerability in grist-core where the `/compare` endpoint allows users with only partial read access to view complete version history changes, exposing data in cells, columns, or tables they should not have permission to see. The vulnerability exists in versions prior to 1.7.7.

MitigationUpgrade to grist-core version 1.7.7 or later to restrict `/compare` endpoint access to users with full read access. Alternatively, remove sensitive document history via `/states/remove` endpoint or block the `/compare` endpoint as a workaround.

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
Grist CoreApplication
Affected:< 1.7.7

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 grist-core version
    Check the installed version of grist-core by inspecting package.json, running 'grist --version' if available, or checking the Docker image tag
    Affected if The installed version is prior to 1.7.7
  2. Verify /compare endpoint exposure
    Inspect server configuration or logs to confirm the /compare endpoint is accessible and not blocked at the proxy or firewall level
    Affected if The /compare endpoint is reachable and the grist-core version is below 1.7.7
  3. Check for document history
    Review whether any grist documents have existing version history or state data that could be accessed through /compare
    Affected if Version history exists in any document and the grist-core version is below 1.7.7 with /compare exposed
  4. Audit user access patterns
    Identify if any users or API keys are configured with partial read access to documents (less than full read permission)
    Affected if Users with partial read access exist and the /compare endpoint is accessible on a vulnerable version

You are affected if grist-core version is below 1.7.7 and the /compare endpoint is accessible to users with partial read access.

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.7.7 or later
Fixed in 1.7.7
Interim mitigation

Upgrade to grist-core version 1.7.7 or later to restrict `/compare` endpoint access to users with full read access. Alternatively, remove sensitive document history via `/states/remove` endpoint or block the `/compare` endpoint as a workaround.

Recommended fix High confidence

Grist Core 1.7.7

  1. 1. Back up your Grist Core data and configuration
  2. 2. Upgrade Grist Core to version 1.7.7 or later
  3. 3. Verify the upgrade was successful by checking the version number
  4. 4. Test that users with partial read access can no longer access the /compare endpoint for documents they don't have full read access to

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

Fix this in Grist Core 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-2025-64753 — 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-64753 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