CVE Intelligence

Udecode vulnerabilities

🔔 Create alert RSS

Published CVEs affecting Udecode products: 3 record(s), with severity, exploitation and fixes.

Exploited only (KEV) →

CVE-2026-88976 Medium · 6.1 CWE-79 Sep 16, 2026
@platejs/core HTML deserialization can trigger browser behavior during parsing
Plate is a rich-text editor with AI and shadcn/ui. Prior to 53.3.11, and in the discontinued 54.0.0-beta.0 through 54.0.0-beta.1 builds, Plate core HTML deserialization APIs parse supplied HTML strings in the active document. When an application passes untrusted or cross-user HTML to these APIs, certain HTML attributes can trigger browser behavior before the HTML is converted into editor nodes. This can allow attacker-controlled script to execute in the consuming application's origin when another user loads the deserialized content. This issue is fixed in version 53.3.11.
CVE-2026-65842 High · 8.2 CWE-918 Aug 20, 2026
Plate: SSRF with response disclosure in DOCX image embedding
Plate is a rich-text editor with AI and shadcn/ui. Prior to 53.3.2, @platejs/docx-io fetches remote image URLs while converting attacker-controlled HTML through htmlToDocxBlob in a server-side or privileged environment. The converter can make requests to internal network resources and include the fetched image bytes in the generated DOCX, allowing server-side request forgery with response disclosure. Applications can also incur resource consumption from attacker-selected remote responses. This issue is fixed in version 53.3.2.
CVE-2026-55596 High · 8.7 CWE-79 Jul 8, 2026
Plate: Media embed provider metadata can bypass URL sanitization and execute iframe JavaScript
Plate is a rich-text editor with AI and shadcn/ui. From 53.0.0 until 53.1.4, the media embed renderer trusts serialized provider or sourceUrl metadata in useMediaState and skips parseMediaUrl protocol validation, allowing a crafted Plate document to set a known video provider while keeping url as a javascript: iframe source that the registry MediaEmbedElement renders directly as an iframe src when a victim opens the document. This issue is fixed in version 53.1.4.