Plate: SSRF with response disclosure in DOCX image embeddingGHSA-4q39-2jhr-7qx8
HIGHFix: udecode/plate#5053GHSA-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.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4q39-2jhr-7qx8.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.
@platejs/docx-ionpmDescription
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-ioversions< 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @platejs/docx-io | all versions | 53.3.2npm install @platejs/docx-io@53.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
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
Is GHSA-4q39-2jhr-7qx8 in your dependencies?
Find it across npm, including transitive dependencies.