{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64752 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64752 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64752 is a medium-severity server-side request forgery vulnerability in gristlabs grist-core, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64752 and fix it if it is affected.\n\nWhat it is: CVE-2025-64752 is a medium-severity server-side request forgery vulnerability in gristlabs grist-core, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-64752 in the wild and no public exploit code.\n\nAffected product: gristlabs grist-core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-64752/ (Markdown: https://insights.sbomify.com/CVE-2025-64752/index.md)","id":"CVE-2025-64752","markdown":"https://insights.sbomify.com/CVE-2025-64752/index.md","name":"CVE-2025-64752","record":{"aliases":["GHSA-qh95-2qv8-pqx3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Grist spreadsheet server","requires_auth":"none","summary":"An authenticated user can trigger server-side requests to arbitrary URLs, potentially accessing internal network resources or sensitive data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"grist-core","vendor":"getgrist"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"grist-core has path to server-side requests via websocket","id":"CVE-2025-64752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"grist-core has insufficient access control in endpoints for comparisons between documents and versions","id":"CVE-2025-64753"},"packages":[],"prev":{"headline":"OpenFGA Improper Policy Enforcement","id":"CVE-2025-64751"},"products":["grist-core"],"published":"2025-11-13","related":[{"cvss_score":9.1,"headline":"pyodide sandbox option is insecure","id":"CVE-2026-24002","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":8.1,"headline":"Cross-site Scripting vulnerability through custom widget URLs and form redirect URLs in grist-core","id":"CVE-2024-56357","kev_date_added":null,"published":"2024-12-20"},{"cvss_score":8.1,"headline":"Cross-site Scripting vulnerability through svg attachment previews in grist-core","id":"CVE-2024-56358","kev_date_added":null,"published":"2024-12-20"},{"cvss_score":8.1,"headline":"Cross-site Scripting vulnerability through HyperLink cells in grist-core","id":"CVE-2024-56359","kev_date_added":null,"published":"2024-12-20"},{"cvss_score":5.3,"headline":"grist-core has insufficient access control in endpoints for comparisons between documents and versions","id":"CVE-2025-64753","kev_date_added":null,"published":"2025-11-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-14","vendors":["gristlabs"]},"summary":"An authenticated user can trigger server-side requests to arbitrary URLs, potentially accessing internal network resources or sensitive data.","url":"https://insights.sbomify.com/CVE-2025-64752/"}