dbcve.org
Grist CoreApplication · Getgrist

CVE-2025-64752

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 access to any document on a Grist installation can use a feature for fetching from a URL that is executed on the server. The privileged network access of server-side requests could offer opportunities for attack escalation. This issue is fixed in version 1.7.7. The mitigation was to use the proxy for untrusted fetches intended for such purposes. As a workaround, avoid making http/https endpoints available to an instance running Grist that expose credentials or operate without credentials.

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 Server-Side Request Forgery (SSRF) vulnerability in grist-core. Users with access to any document can trigger the server to make arbitrary HTTP/HTTPS requests to internal or external resources via a URL fetching feature, exploiting the privileged network access of server-side requests for potential attack escalation.

MitigationUpgrade to version 1.7.7 and ensure the proxy is used for untrusted fetches. As a workaround, avoid exposing http/https endpoints to the Grist instance that contain credentials or operate without authentication.

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 installed Grist Core version
    Check the package.json file in the grist-core installation directory, or inspect the Docker image tag if running containerized. Run: npm list grist-core or grep version in package.json
    Affected if version is below 1.7.7 (e.g., 1.7.6, 1.7.5, etc.)
  2. Confirm URL fetching feature exists and is accessible
    Grist Core includes a URL fetching capability in its document editor. Verify the feature is available by checking if users with document access can insert or reference external URLs using the FETCH formula or URL import functionality
    Affected if the URL fetching feature is present and accessible to non-admin users with document-level access
  3. Check server network posture
    Review whether the Grist server has access to internal network resources, cloud metadata endpoints, or sensitive internal services. Inspect any configured proxy settings in grist configuration files
    Affected if the server can reach internal resources (e.g., 127.0.0.1, 169.254.169.254 for cloud metadata, or internal LAN addresses) that should not be exposed to users
  4. Audit user access controls
    Determine if any user accounts exist with permission to create or edit documents in Grist. List users and their document access levels using the Grist admin panel or API
    Affected if there are users with document create/edit permissions who could invoke the URL fetching feature

You are affected if running Grist Core version below 1.7.7 and any user with document access can trigger server-side URL requests that reach internal or sensitive network resources.

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 version 1.7.7 and ensure the proxy is used for untrusted fetches. As a workaround, avoid exposing http/https endpoints to the Grist instance that contain credentials or operate without authentication.

Recommended fix High confidence

1.7.7

  1. 1. Back up your Grist Core data and configuration files before upgrading.
  2. 2. Stop the Grist Core service to prevent data corruption during the upgrade.
  3. 3. Upgrade Grist Core to version 1.7.7 or later. If using a package manager, run the equivalent of: pip install grist-core==1.7.7 or docker pull gristlabs/grist:1.7.7
  4. 4. Verify the upgrade was successful by checking the installed version (e.g., grist --version or checking the Docker container version).
  5. 5. Restart the Grist Core service.
  6. 6. Test that the application functions normally with a test document.

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

Fix this in Grist Core Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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