Skip to content
Web

CVE-2026-55596

8.7
High
EPSS 0.43%Patch availableJul 9, 2026

RCE via trusted media embed in Plate editor allowing javascript: iframe execution.

common questions

Is CVE-2026-55596 being exploited?

Not confirmed. CVE-2026-55596 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.

How severe is CVE-2026-55596?

CVE-2026-55596 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-55596?

Yes. A fix has been recorded for CVE-2026-55596. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55596 affect?

CVE-2026-55596 affects Plate rich-text editor versions 53.0.0 through 53.1.3 (fixed in 53.1.4), Web applications embedding Plate MediaEmbedElement. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55596?

Upgrade Plate to >=53.1.4 and block/sanitize javascript: media URLs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Plate rich-text editor versions 53.0.0 through 53.1.3 (fixed in 53.1.4)Web applications embedding Plate MediaEmbedElement
impact

Stored XSS / remote code execution: crafted Plate document can set iframe src to javascript:, executing attacker script when opened, enabling data theft/session hijack.

action required

Immediate action required

affected versions
udecode plate
  • affected>= 53.0.0 and < 53.1.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free