Vulnerabilities in pkg:npm/@platejs/media

PACKAGE
Advisory Identifier: GHSA-qj6x-xx2h-8hvv
Advisory Summary

CVE-2026-55596 is a HIGH (CVSS 8.7) media embed provider metadata can vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Plate libraries in the npm ecosystem. The issue involves media embed provider metadata can bypass url sanitization and execute iframe javascript. Remediation is available by upgrading affected packages to version 53.1.4.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@platejs/media

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@platejs/media. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-qj6x-xx2h-8hvv CVE-2026-55596 HIGH Plate: Media embed provider metadata can bypass URL sanitization and execute iframe JavaScript

CVE-2026-55596 at a Glance

CVE Identifier CVE-2026-55596
GHSA Identifier GHSA-qj6x-xx2h-8hvv
Severity HIGH
CVSS v3.1 Base Score 8.7
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Plate
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-55596

To remediate this vulnerability, upgrade all affected Plate dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@platejs/media fixed: 53.1.4
npm install @platejs/media@53.1.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @platejs/media

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-55596, inspect your project dependencies using npm:

npm ls @platejs/media

Analyze the terminal output to locate any version of Plate in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 53.1.4), your application is affected.

Note: The npm ls @platejs/media command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Plate, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The media embed renderer trusts serialized `provider` or `sourceUrl` metadata and skips the URL protocol validation that normally blocks unsafe media embed URLs. A crafted Plate document can set a known video provider while keeping `url` as a `javascript:` iframe source. When a victim opens that document in an app using the registry media embed component, the component renders the attacker URL directly as an iframe `src`. ## Impact An attacker who can create or share Plate document content with another user can execute JavaScript in the victim browser context when the victim opens the document. This can expose application data available to the page and perform actions as the victim, depending on the host application's session model. ## Reproduction Use a Plate editor or viewer that renders media embeds with the registry `MediaEmbedElement` and load a document containing this node: ```json { "type": "media_embed", "provider": "vimeo", "sourceUrl": "https://vimeo.com/1", "url": "javascript:parent.postMessage('plate-media-xss','*')", "children": [{ "text": "" }] } ``` When rendered, the node is treated as a Vimeo media embed because `provider` is present. The iframe receives the unvalidated `url` value as its `src`. ## Root Cause / Technical Details `parseMediaUrl` is the intended hardening point for media embed URLs and rejects parser output unless the URL protocol is `http:` or `https:`. However, `useMediaState` had a fast path for serialized nodes that already contain `provider` or `sourceUrl`. That fast path returned `{ id, provider, sourceUrl, url }` directly and did not call `parseMediaUrl` or otherwise validate the stored `url`. The registry `MediaEmbedElement` then checks that `embed.provider` is one of the video providers and renders non-YouTube video providers with `<iframe src={embed.url}>`. Because `provider` is attacker-controlled serialized document metadata, it can be set to `vimeo` while `url` remains `javascript:...`. This is fixed in `@platejs/media` 53.1.4 by recomputing embed metadata from the render URL instead of trusting serialized `provider`, `id`, or `sourceUrl` metadata. ## PoC Evidence A browser proof using the same data flow set an iframe `src` to: ```text javascript:parent.postMessage('plate-media-xss','*') ``` Chromium executed the iframe JavaScript and the parent page received `plate-media-xss`, confirming execution from the iframe source. ## Remediation Upgrade `@platejs/media` to 53.1.4 or later. Treat `provider`, `sourceUrl`, and `id` in serialized documents as untrusted derived metadata. Recompute embed metadata from `url` with `parseMediaUrl`, or at minimum validate any fast-path `url` with the same protocol allowlist before rendering an iframe.

CVE-2026-55596 Affected Plate Versions

1 component(s)
Fixed Versions:
53.1.4
Product / Package Ecosystem Affected Versions Fixed Version
@platejs/media
npm
≥ 53.0.0
< 53.1.4
53.1.4

References

Frequently Asked Questions

What is CVE-2026-55596?
CVE-2026-55596 is a security vulnerability in Plate involving Media embed provider metadata can bypass URL sanitization and execute iframe JavaScript under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Plate versions are affected?
Affected versions include releases prior to 53.1.4 across affected packages: @platejs/media.
What version fixes CVE-2026-55596?
Upgrading to 53.1.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @platejs/media affected?
Yes, @platejs/media is affected in releases prior to 53.1.4. Upgrade your dependency to 53.1.4 or later.
What is the CVSS score of CVE-2026-55596?
CVE-2026-55596 has a CVSS v3.1 base score of 8.7 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2026-55596?
CVE-2026-55596 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check npm dependencies for CVE-2026-55596?
Run the dependency tree command: 'npm ls @platejs/media'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qj6x-xx2h-8hvv",
  "modified" : "2026-08-25T16:29:25Z",
  "published" : "2026-08-25T16:29:25Z",
  "aliases" : [ "CVE-2026-55596" ],
  "summary" : "Plate: Media embed provider metadata can bypass URL sanitization and execute iframe JavaScript",
  "details" : "## Summary\n\nThe media embed renderer trusts serialized `provider` or `sourceUrl` metadata and skips the URL protocol validation that normally blocks unsafe media embed URLs. A crafted Plate document can set a known video provider while keeping `url` as a `javascript:` iframe source. When a victim opens that document in an app using the registry media embed component, the component renders the attacker URL directly as an iframe `src`.\n\n## Impact\n\nAn attacker who can create or share Plate document content with another user can execute JavaScript in the victim browser context when the victim opens the document. This can expose application data available to the page and perform actions as the victim, depending on the host application's session model.\n\n## Reproduction\n\nUse a Plate editor or viewer that renders media embeds with the registry `MediaEmbedElement` and load a document containing this node:\n\n```json\n{\n  \"type\": \"media_embed\",\n  \"provider\": \"vimeo\",\n  \"sourceUrl\": \"https://vimeo.com/1\",\n  \"url\": \"javascript:parent.postMessage('plate-media-xss','*')\",\n  \"children\": [{ \"text\": \"\" }]\n}\n```\n\nWhen rendered, the node is treated as a Vimeo media embed because `provider` is present. The iframe receives the unvalidated `url` value as its `src`.\n\n## Root Cause / Technical Details\n\n`parseMediaUrl` is the intended hardening point for media embed URLs and rejects parser output unless the URL protocol is `http:` or `https:`. However, `useMediaState` had a fast path for serialized nodes that already contain `provider` or `sourceUrl`. That fast path returned `{ id, provider, sourceUrl, url }` directly and did not call `parseMediaUrl` or otherwise validate the stored `url`.\n\nThe registry `MediaEmbedElement` then checks that `embed.provider` is one of the video providers and renders non-YouTube video providers with `<iframe src={embed.url}>`. Because `provider` is attacker-controlled serialized document metadata, it can be set to `vimeo` while `url` remains `javascript:...`.\n\nThis is fixed in `@platejs/media` 53.1.4 by recomputing embed metadata from the render URL instead of trusting serialized `provider`, `id`, or `sourceUrl` metadata.\n\n## PoC Evidence\n\nA browser proof using the same data flow set an iframe `src` to:\n\n```text\njavascript:parent.postMessage('plate-media-xss','*')\n```\n\nChromium executed the iframe JavaScript and the parent page received `plate-media-xss`, confirming execution from the iframe source.\n\n## Remediation\n\nUpgrade `@platejs/media` to 53.1.4 or later. Treat `provider`, `sourceUrl`, and `id` in serialized documents as untrusted derived metadata. Recompute embed metadata from `url` with `parseMediaUrl`, or at minimum validate any fast-path `url` with the same protocol allowlist before rendering an iframe.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@platejs/media"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "53.0.0"
      }, {
        "fixed" : "53.1.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/udecode/plate/security/advisories/GHSA-qj6x-xx2h-8hvv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-55596"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/udecode/plate/pull/5014"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/udecode/plate/commit/6214914ca811adf22d0ad503154494216eed68ba"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/udecode/plate"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/udecode/plate/releases/tag/v53.1.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-25T16:29:25Z",
    "nvd_published_at" : "2026-07-08T21:16:50Z"
  }
}