Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

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

GHSA-x7m8-jrm8-hpvx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@eigenpal/docx-editor-react 1.8.3; @eigenpal/docx-editor-core 1.8.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Impact 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. Remediation 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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-x7m8-jrm8-hpvx

  2. Revision 2 · amended ·

    Amended from osv record GHSA-x7m8-jrm8-hpvx

  3. Revision 1 · created ·

    Published from ghsa record GHSA-x7m8-jrm8-hpvx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-x7m8-jrm8-hpvx

Advisory: @eigenpal/docx-editor-react: CSS injection and print-time XSS via unescaped embedded font-family name
IDs: GHSA-x7m8-jrm8-hpvx
Record: https://patchnext.com/advisories/ghsa-x7m8-jrm8-hpvx (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @eigenpal/docx-editor-react 1.8.3; @eigenpal/docx-editor-core 1.8.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @eigenpal/docx-editor-react: affected <= 1.8.2; fixed in 1.8.3
- npm @eigenpal/docx-editor-core: affected <= 1.8.2; fixed in 1.8.3

## Suggested inspection (read-only)
- `npm ls @eigenpal/docx-editor-react --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @eigenpal/docx-editor-core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @eigenpal/docx-editor-react, @eigenpal/docx-editor-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x7m8-jrm8-hpvx (GitHub-reviewed advisory GHSA-x7m8-jrm8-hpvx lists affected ranges: npm @eigenpal/docx-editor-core >=0 =0 <=1.8.2)
- Verified: https://osv.dev/vulnerability/GHSA-x7m8-jrm8-hpvx (OSV record GHSA-x7m8-jrm8-hpvx lists affected ranges: npm @eigenpal/docx-editor-core >=0 =0 <1.8.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…