How severe is GHSA-4q39-2jhr-7qx8?

GHSA-4q39-2jhr-7qx8 has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4q39-2jhr-7qx8?

GHSA-4q39-2jhr-7qx8 affects the following packages: @platejs/docx-io (npm). Ecosystems affected: npm.

How do I fix GHSA-4q39-2jhr-7qx8?

Update @platejs/docx-io to 53.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4q39-2jhr-7qx8 is resolved across your whole dependency graph.

How do I detect GHSA-4q39-2jhr-7qx8 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @platejs/docx-io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4q39-2jhr-7qx8 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-4q39-2jhr-7qx8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4q39-2jhr-7qx8 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.

What is the EPSS score for GHSA-4q39-2jhr-7qx8?

GHSA-4q39-2jhr-7qx8 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4q39-2jhr-7qx8?

GHSA-4q39-2jhr-7qx8 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-4q39-2jhr-7qx8 published, and has it been updated?

GHSA-4q39-2jhr-7qx8 was published on September 2, 2026 and was last updated on September 2, 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-4q39-2jhr-7qx8 — @platejs/docx-io

HIGHFix: udecode/plate#5053

GHSA-4q39-2jhr-7qx8 is a high-severity (CVSS 8.2) Server-Side Request Forgery (SSRF) vulnerability in @platejs/docx-io. A fix is available for @platejs/docx-io — see the affected versions and patch details below.

Plate: SSRF with response disclosure in DOCX image embedding

Also known asCVE-2026-65842

Published

Sep 2, 2026

Updated

Sep 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-4q39-2jhr-7qx8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 382,795 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@platejs/docx-ionpm

46Kdownloads / week

Description

Summary

@platejs/docx-io can fetch remote image URLs while converting HTML to DOCX. When an application converts attacker-controlled HTML in a server-side or privileged environment, this can cause the application environment to make unintended outbound requests and include fetched image data in the generated DOCX.

Impact

Applications are affected when they use @platejs/docx-io to convert untrusted HTML that may contain remote image references, especially in server-side conversion workflows or environments with access to internal network resources.

Affected package:

@platejs/docx-io versions < 53.3.2

Patched versions

Upgrade to @platejs/docx-io version 53.3.2 or later.

Workarounds

If you cannot upgrade immediately, do not pass untrusted HTML with remote image URLs to DOCX export. Sanitize untrusted HTML to remove remote image references, convert trusted images to data URIs before conversion, or run conversion in an environment with restricted outbound network access.

Credits

Thanks to EQSTLab for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@platejs/docx-io`	all versions	53.3.2`npm install @platejs/docx-io@53.3.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @platejs/docx-io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @platejs/docx-io to 53.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4q39-2jhr-7qx8 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

## Summary `@platejs/docx-io` can fetch remote image URLs while converting HTML to DOCX. When an application converts attacker-controlled HTML in a server-side or privileged environment, this can cause the application environment to make unintended outbound requests and include fetched image data in the generated DOCX. ## Impact Applications are affected when they use `@platejs/docx-io` to convert untrusted HTML that may contain remote image references, especially in server-side conversion workflows or environments with access to internal network resources. Affected package: - `@platejs/d