EUVD-2026-43045Severity by source
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
Network-reachable link injection with low complexity; PR:N reflects the unauthenticated select-account vector, UI:R for the required click, high C/I as script acts with victim's API rights, no availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
3DescriptionCVE.org
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.
Articles & Coverage 1
AnalysisAI
Stored and reflected cross-site scripting in Grist (grist-core) before 1.7.15 lets an attacker place a javascript: URL into an unvalidated link href and execute script in a victim's authenticated Grist origin on a single click. Two entry points are affected: the /welcome/select-account page reflects its next query parameter into account-button links, and the GristDocTour table's Link_URL column renders as a clickable tour button, so a document editor can plant a payload that runs when another user opens the document. Because the script executes as the victim, it can drive Grist APIs to read or modify data and change sharing/access rules, letting an editor escalate to owner-level control. There is no public exploit identified at time of analysis and it is not in CISA KEV.
Technical ContextAI
Grist is a self-hosted/open-source spreadsheet-database hybrid (gristlabs:grist-core) that uses Python as its formula language and exposes a REST API scoped to the authenticated user session. The root cause is CWE-79 (improper neutralization of input during web page generation): attacker-controlled values are assigned to an anchor element's href without validating the URL scheme, so a javascript: URI is treated as an executable link rather than a navigable resource. One sink is the next redirect parameter on /welcome/select-account (classic reflected DOM/link injection); the other is application data - the Link_URL column of the special GristDocTour table - which is rendered into a clickable button, turning an ordinary editable document field into a persistent script-injection vector. Neither sink applies scheme allow-listing (http/https/mailto), which is the standard mitigation for user-supplied link targets.
RemediationAI
Vendor-released patch: upgrade to Grist grist-core version 1.7.15 or later, which adds URL scheme validation to both link sinks (fix commit 5d0a90a162b5125fce7e8a86fb137eee5199dbde, release https://github.com/gristlabs/grist-core/releases/tag/v1.7.15, advisory https://github.com/gristlabs/grist-core/security/advisories/GHSA-7f6v-vghq-34xq). If you cannot upgrade immediately, reduce exposure by limiting who holds editor rights on shared documents (this directly removes the persistent GristDocTour Link_URL vector, at the cost of collaborative editing), auditing existing GristDocTour tables for javascript: values in Link_URL and clearing them, and treating /welcome/select-account links containing an attacker-supplied next parameter as untrusted - avoid distributing or clicking such links and consider fronting the app with a proxy/WAF rule that blocks next values beginning with javascript: (may break legitimate deep-link redirects). These are stopgaps only; upgrading to 1.7.15 is the reliable fix.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser
pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi
The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python
BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.
Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301
In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne
Cross-user flow execution in Langflow (< 1.9.1) lets any authenticated API-key holder run another user's flow by passing
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today