How severe is GHSA-x7m8-jrm8-hpvx?

GHSA-x7m8-jrm8-hpvx has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x7m8-jrm8-hpvx?

GHSA-x7m8-jrm8-hpvx affects the following packages: @eigenpal/docx-editor-core (npm), @eigenpal/docx-editor-react (npm). Ecosystems affected: npm.

How do I fix GHSA-x7m8-jrm8-hpvx?

Update @eigenpal/docx-editor-core to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7m8-jrm8-hpvx is resolved across your whole dependency graph.

How do I detect GHSA-x7m8-jrm8-hpvx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @eigenpal/docx-editor-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-x7m8-jrm8-hpvx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-x7m8-jrm8-hpvx?

O3 pinpoints whether GHSA-x7m8-jrm8-hpvx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-x7m8-jrm8-hpvx actively exploited in the wild?

No public exploit code has been indexed for GHSA-x7m8-jrm8-hpvx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-x7m8-jrm8-hpvx published, and has it been updated?

GHSA-x7m8-jrm8-hpvx was published on September 10, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

GHSA-x7m8-jrm8-hpvx

HIGH

GHSA-x7m8-jrm8-hpvx is a high-severity (CVSS 8.1) vulnerability in @eigenpal/docx-editor-core. O3 Security confirms whether GHSA-x7m8-jrm8-hpvx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Published

Sep 10, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

📦@eigenpal/docx-editor-core📦@eigenpal/docx-editor-react

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@eigenpal/docx-editor-core`	all versions	1.8.3
📦npm	`@eigenpal/docx-editor-react`	all versions	1.8.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @eigenpal/docx-editor-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @eigenpal/docx-editor-core to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7m8-jrm8-hpvx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x7m8-jrm8-hpvx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-x7m8-jrm8-hpvx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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 b

O3 Security · Impact-Aware SCA

Is GHSA-x7m8-jrm8-hpvx in your dependencies?

O3 detects GHSA-x7m8-jrm8-hpvx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works