<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T19:49:27.975171+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-6352</id>
    <title>EUVD-2026-6352</title>
    <updated>2026-10-12T19:49:28.024471+00:00</updated>
    <content>EUVD-2026-6352</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-6352"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-40631</id>
    <title>fkie_cve-2024-40631</title>
    <updated>2026-10-12T19:49:28.024507+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Plate media is an open source, rich-text editor for React. Editors that use `MediaEmbedElement` and pass custom `urlParsers` to the `useMediaState` hook may be vulnerable to XSS if a custom parser allows `javascript:`, `data:` or `vbscript:` URLs to be embedded. Editors that do not use `urlParsers` and consume the `url` property directly may also be vulnerable if the URL is not sanitised. The default parsers `parseTwitterUrl` and `parseVideoUrl` are not affected. `@udecode/plate-media` 36.0.10 resolves this issue by only allowing HTTP and HTTPS URLs during parsing. This affects only the `embed` property returned from `useMediaState`. In addition, the `url` property returned from `useMediaState` has been renamed to `unsafeUrl` to indicate that it has not been sanitised. The `url` property on `element` is also unsafe, but has not been renamed. If you're using either of these properties directly, you will still need to validate the URL yourself. Users are advised to upgrade. Users unable to upgrade should ensure that any custom `urlParsers` do not allow `javascript:`, `data:` or `vbscript:` URLs to be returned in the `url` property of their return values. If `url` is consumed directly, validate the URL protocol before passing it to the `iframe` element.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-40631"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-h3pq-667x-r789</id>
    <title>GHSA-h3pq-667x-r789 — Plate media plugins has a XSS in media embed element when using custom URL parsers</title>
    <updated>2026-10-12T19:49:28.024546+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @udecode/plate-media</p>
<p>### Impact
Editors that use `MediaEmbedElement` and pass custom `urlParsers` to the `useMediaState` hook may be vulnerable to XSS if a custom parser allows `javascript:`, `data:` or `vbscript:` URLs to be embedded. Editors that do not use `urlParsers` and instead consume the `url` property directly may also be vulnerable if the URL is not sanitised.</p>
<p>The default parsers `parseTwitterUrl` and `parseVideoUrl` are not affected.</p>
<p>Examples of vulnerable code:</p>
<p>```tsx
const { embed } = useMediaState({
  urlParsers: [
    // Custom parser that does not use an allowlist or validate the URL protocol
    (url) =&gt; ({ url }),
  ],
});</p>
<p>return (
  &lt;iframe
    src={embed!.url}
    // ...
  /&gt;
);
```</p>
<p>```tsx
const { url } = useMediaState();</p>
<p>return (
  &lt;iframe
    // url property used directly from useMediaState() with no sanitisation
    src={url}
    // ...
  /&gt;
);
```</p>
<p>```tsx
const { url } = element;</p>
<p>return (
  &lt;iframe
    // url property used directly from element with no sanitisation
    src={url}
    // ...
  /&gt;
);
```</p>
<p>### Patches
`@udecode/plate-media` 36.0.10 resolves this issue by only allowing HTTP and HTTPS URLs during parsing. This affects only the `embed` property returned from `useMediaState`.</p>
<p>In addition, the `url` property returned from `useMediaState` has been renamed to `unsafeUrl` to indicate that it has not been sanitised. The `url` property on `element` is also unsafe, but has not been renamed. If you're using either of these properties directly, you will still nee…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-h3pq-667x-r789"/>
  </entry>
</feed>
