<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 12 Oct 2026 23:12:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-6352</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-6352</link>
      <description>EUVD-2026-6352</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-6352</guid>
    </item>
    <item>
      <title>fkie_cve-2024-40631</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-40631</link>
      <description>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-40631</guid>
    </item>
    <item>
      <title>GHSA-h3pq-667x-r789 — Plate media plugins has a XSS in media embed element when using custom URL parsers</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h3pq-667x-r789</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @udecode/plate-media&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;The default parsers `parseTwitterUrl` and `parseVideoUrl` are not affected.&lt;/p&gt;
&lt;p&gt;Examples of vulnerable code:&lt;/p&gt;
&lt;p&gt;```tsx
const { embed } = useMediaState({
  urlParsers: [
    // Custom parser that does not use an allowlist or validate the URL protocol
    (url) =&amp;gt; ({ url }),
  ],
});&lt;/p&gt;
&lt;p&gt;return (
  &amp;lt;iframe
    src={embed!.url}
    // ...
  /&amp;gt;
);
```&lt;/p&gt;
&lt;p&gt;```tsx
const { url } = useMediaState();&lt;/p&gt;
&lt;p&gt;return (
  &amp;lt;iframe
    // url property used directly from useMediaState() with no sanitisation
    src={url}
    // ...
  /&amp;gt;
);
```&lt;/p&gt;
&lt;p&gt;```tsx
const { url } = element;&lt;/p&gt;
&lt;p&gt;return (
  &amp;lt;iframe
    // url property used directly from element with no sanitisation
    src={url}
    // ...
  /&amp;gt;
);
```&lt;/p&gt;
&lt;p&gt;### 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`.&lt;/p&gt;
&lt;p&gt;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&amp;#39;re using either of these properties directly, you will still nee…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @udecode/plate-media&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;The default parsers `parseTwitterUrl` and `parseVideoUrl` are not affected.&lt;/p&gt;
&lt;p&gt;Examples of vulnerable code:&lt;/p&gt;
&lt;p&gt;```tsx
const { embed } = useMediaState({
  urlParsers: [
    // Custom parser that does not use an allowlist or validate the URL protocol
    (url) =&amp;gt; ({ url }),
  ],
});&lt;/p&gt;
&lt;p&gt;return (
  &amp;lt;iframe
    src={embed!.url}
    // ...
  /&amp;gt;
);
```&lt;/p&gt;
&lt;p&gt;```tsx
const { url } = useMediaState();&lt;/p&gt;
&lt;p&gt;return (
  &amp;lt;iframe
    // url property used directly from useMediaState() with no sanitisation
    src={url}
    // ...
  /&amp;gt;
);
```&lt;/p&gt;
&lt;p&gt;```tsx
const { url } = element;&lt;/p&gt;
&lt;p&gt;return (
  &amp;lt;iframe
    // url property used directly from element with no sanitisation
    src={url}
    // ...
  /&amp;gt;
);
```&lt;/p&gt;
&lt;p&gt;### 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`.&lt;/p&gt;
&lt;p&gt;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&amp;#39;re using either of these properties directly, you will still nee…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h3pq-667x-r789</guid>
    </item>
  </channel>
</rss>
