What is the CVSS score of CVE-2026-55596?

CVE-2026-55596 has a CVSS 3.1 base score of 8.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.2%.

Which versions of Plate are affected by CVE-2026-55596?

Plate rich-text editor versions 53.0.0 through 53.1.3 contain a stored cross-site scripting vulnerability that allows arbitrary JavaScript execution when users open crafted documents, affecting any…. A patch is available.

Is there a public PoC exploit available for CVE-2026-55596?

Yes, a public proof-of-concept exploit is available for CVE-2026-55596. Prioritise patching immediately. EPSS: 0.2%.

How to fix or mitigate CVE-2026-55596?

Within 24 hours: Inventory all applications and systems using Plate rich-text editor and identify running versions. Within 7 days: Upgrade all instances to Plate version 53.1.4 (which contains the fix). Within 30 days: Audit document handling workflows, review access logs for suspicious document opens during the vulnerability window, and implement document provenance controls.

Plate CVE-2026-55596

EUVD-2026-42395 HIGH

Cross-site Scripting (XSS) (CWE-79)

2026-07-08 security-advisories@github.com

GHSA-qj6x-xx2h-8hvv

XSS

8.7

CVSS 3.1 · Vendor: github

Severity by source

Vendor (github) PRIMARY

8.7 HIGH

AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Primary rating from Vendor (github) · only source for this CVE.

CVSS VectorVendor: github

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch available

Jul 08, 2026 - 22:04 EUVD

Analysis Generated

Jul 08, 2026 - 21:41 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on @platejs/media (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 53.0.0.

DescriptionCVE.org

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.

AnalysisAI

Stored cross-site scripting in the Plate rich-text editor (versions 53.0.0 through 53.1.3) lets a crafted document execute attacker JavaScript when a victim opens it. The media embed renderer trusts serialized provider/sourceUrl metadata in useMediaState and skips parseMediaUrl protocol validation, so an attacker can flag a URL as a legitimate video provider while keeping a javascript: payload that MediaEmbedElement renders directly as an iframe src. No public exploit has been identified at time of analysis, and the flaw is fixed in 53.1.4.