SSRF (Server-Side Request Forgery) in @platejs/docx-io (CVE-2026-65842)
Summary
SSRF in @platejs/docx-io (CVE-2026-65842). Confidential information can be exposed externally. Mitigation: upgrade to 53.3.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65842 has been found in @platejs/docx-io.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade @platejs/docx-io to 53.3.2 or later.
If unsure, ask your IT team or search "@platejs/docx-io CVE-2026-65842" on the vendor's site.
CVE-2026-65842 (@platejs/docx-io) — CWE-918 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 53.3.2 — apply immediately
Workaround: If you cannot upgrade immediately, do not pass untrusted HTML with remote image URLs to DOCX export.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in @platejs/docx-io.
Check the vendor advisory for the affected versions of @platejs/docx-io.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 53.3.2.
Workaround: If you cannot upgrade immediately, do not pass untrusted HTML with remote image URLs to DOCX export.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@platejs/docx-io' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@platejs/docx-io' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@platejs/docx-ioを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If you cannot upgrade immediately, do not pass untrusted HTML with remote image URLs to DOCX export.パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, do not pass untrusted HTML with remote image URLs to DOCX export. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @platejs/docx-io to 53.3.2ステージング環境で 53.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com