Skip to main content
VulnerabilityPublished

CVE-2026-65842: udecode plate · Server-Side Request Forgery (SSRF)

Affects udecode plateSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 53.3.2 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 53.3.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade udecode plate to 53.3.2.

Affected software

ProductAffectedFixed in
udecodeplateAffected
  • <53.3.2
Fixed in
  • 53.3.2

AI-suggested

Upgrade to udecode plate version 53.3.2 or later, where this SSRF vulnerability is fixed. No additional mitigation steps are required once the update is applied.

Description

CVE-2026-65842 is a Server-Side Request Forgery (SSRF) vulnerability in the udecode plate rich-text editor prior to version 53.3.2. The vulnerability arises from the @platejs/docx-io component fetching remote image URLs during HTML to DOCX conversion in server-side or privileged environments. This allows attackers to make requests to internal network resources and include the fetched image data in generated DOCX files, potentially disclosing internal responses and causing resource consumption. The issue is fixed in version 53.3.2.

References

Community reviews

Loading reviews…