Summary
@grackle-ai/server: Unescaped Error String in renderPairingPage() HTML Template
Workarounds
No workaround needed, all current callers pass hardcoded strings.
Resources
- CWE-79: Improper Neutralization of Input During Web Page Generation
- File:
packages/server/src/index.ts
Impact
The renderPairingPage() function embeds the error parameter directly into HTML without escaping:
const errorHtml = error ? `<p style="color:#e74c3c">${error}</p>` : "";
All current call sites pass hardcoded strings, so this is not exploitable today. However, the function is architecturally fragile, if a future code change passes user-controlled or dynamic content into the error parameter, it would create an XSS vulnerability.
The renderAuthorizePage() function in the same file correctly uses escapeHtml() for dynamic content, making this an inconsistency.
Affected code:
packages/server/src/index.ts:64-89,renderPairingPage()with unescaped error interpolation- Compare:
packages/server/src/index.ts:130,renderAuthorizePage()correctly usesescapeHtml()
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
v0.70.1
Fix: Apply escapeHtml() to the error parameter:
const errorHtml = error ? `<p style="color:#e74c3c">${escapeHtml(error)}</p>` : "";
Frequently Asked Questions
- What is GHSA-7Q9X-8G6P-3X75? GHSA-7Q9X-8G6P-3X75 is a low-severity cross-site scripting (XSS) vulnerability in @grackle-ai/server (npm), affecting versions <= 0.70.0. It is fixed in 0.70.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of @grackle-ai/server are affected by GHSA-7Q9X-8G6P-3X75? @grackle-ai/server (npm) versions <= 0.70.0 is affected.
- Is there a fix for GHSA-7Q9X-8G6P-3X75? Yes. GHSA-7Q9X-8G6P-3X75 is fixed in 0.70.1. Upgrade to this version or later.
- Is GHSA-7Q9X-8G6P-3X75 exploitable, and should I be worried? Whether GHSA-7Q9X-8G6P-3X75 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-7Q9X-8G6P-3X75 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-7Q9X-8G6P-3X75? Upgrade
@grackle-ai/serverto 0.70.1 or later.