Categories
CVE-2026-55596 high CVSS 8.7

Cross-Site Scripting (XSS) in @platejs/media (CVE-2026-55596)

Summary

Cross-site scripting in @platejs/media (CVE-2026-55596). Confidential information can be exposed externally. Exploitable via provider. Mitigation: upgrade to 53.1.4 or later.

Original description

The description as published by the source.

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.

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-55596 has been found in @platejs/media.
Attackers can target a specific entry point like provider over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade @platejs/media to 53.1.4 or later.
If unsure, ask your IT team or search "@platejs/media CVE-2026-55596" on the vendor's site.

CVE-2026-55596 (@platejs/media) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: provider / sourceUrl / url / src
Patched: 53.1.4 — apply immediately
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.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in @platejs/media. Attackers reach the vulnerable code path via provider.

📍 Affected scope

Check the vendor advisory for the affected versions of @platejs/media. Attack surface: provider / sourceUrl / url / src.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 53.1.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@platejs/media' . 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

  1. 1
    Identify exposure identify
    grep -r '@platejs/media' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @platejs/media を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade @platejs/media to 53.1.4

    ステージング環境で 53.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @platejs/media
[{"type":"SEMVER","events":[{"introduced":"53.0.0"},{"fixed":"53.1.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details