GHSA-X7M8-JRM8-HPVX

@eigenpal/docx-editor-react: CSS injection and print-time XSS via unescaped embedded font-family name

Embedded font-family names (word/fontTable.xml) were interpolated unescaped into an injected @font-face <style> and into the print window's document.write(). A crafted name injects page-wide CSS on open, and breaks out of <style>
into executable HTML on Print.

Opening a crafted .docx applies attacker-controlled CSS page-wide with zero clicks (overlay/phishing, attribute-selector exfiltration of input values, tracking beacons). Clicking Print escalates to script execution in the embedder's origin.

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.

GHSA-X7M8-JRM8-HPVX has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Upgrade to 1.8.3. Font names are CSS-escaped before interpolation (quotes, backslash, < >, and CSS newlines), and the print window is assembled with DOM APIs instead of document.write.

1. What is GHSA-X7M8-JRM8-HPVX? GHSA-X7M8-JRM8-HPVX is a high-severity cross-site scripting (XSS) vulnerability in @eigenpal/docx-editor-core (npm), affecting versions <= 1.8.2. It is fixed in 1.8.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is GHSA-X7M8-JRM8-HPVX? GHSA-X7M8-JRM8-HPVX has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by GHSA-X7M8-JRM8-HPVX?
   • @eigenpal/docx-editor-core (npm) (versions <= 1.8.2)
   • @eigenpal/docx-editor-react (npm) (versions <= 1.8.2)
4. Is there a fix for GHSA-X7M8-JRM8-HPVX? Yes. GHSA-X7M8-JRM8-HPVX is fixed in 1.8.3. Upgrade to this version or later.
5. Is GHSA-X7M8-JRM8-HPVX exploitable, and should I be worried? Whether GHSA-X7M8-JRM8-HPVX 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
6. What actually determines whether GHSA-X7M8-JRM8-HPVX 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.
7. How do I fix GHSA-X7M8-JRM8-HPVX?
   • Upgrade @eigenpal/docx-editor-core to 1.8.3 or later
   • Upgrade @eigenpal/docx-editor-react to 1.8.3 or later