<?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>Fri, 02 Oct 2026 12:10:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-343454</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-343454</link>
      <description>EUVD-2026-343454</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-343454</guid>
    </item>
    <item>
      <title>fkie_cve-2026-58263</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-58263</link>
      <description>&lt;p&gt;Jodit Editor is a WYSIWYG editor with a built-in file browser &amp;amp; image editor. In versions prior to 4.12.28, the built-in clean-html sanitizer can be bypassed by a MathML/&amp;lt;style&amp;gt; carrier that hides a dangerous element from the sanitizer&amp;#39;s element walk, so a no-interaction event handler survives into the editor value, potentially causing Mutation XSS. When an application supplies attacker-influenced HTML to the editor&amp;#39;s value-set or insertion paths, the sanitized output still contains a live &amp;lt;img ... onload=...&amp;gt; (or another non-onerror handler such as onfocus). A consumer that renders that output (element.innerHTML = editor.value) executes the handler with no user interaction. This issue has been fixed in version 4.12.28.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Jodit Editor is a WYSIWYG editor with a built-in file browser &amp;amp; image editor. In versions prior to 4.12.28, the built-in clean-html sanitizer can be bypassed by a MathML/&amp;lt;style&amp;gt; carrier that hides a dangerous element from the sanitizer&amp;#39;s element walk, so a no-interaction event handler survives into the editor value, potentially causing Mutation XSS. When an application supplies attacker-influenced HTML to the editor&amp;#39;s value-set or insertion paths, the sanitized output still contains a live &amp;lt;img ... onload=...&amp;gt; (or another non-onerror handler such as onfocus). A consumer that renders that output (element.innerHTML = editor.value) executes the handler with no user interaction. This issue has been fixed in version 4.12.28.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-58263</guid>
    </item>
    <item>
      <title>GHSA-rxcw-mc6f-6hr3 — Jodit Editor: Mutation XSS in jodit clean-html via a MathML/style rawtext carrier</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rxcw-mc6f-6hr3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: jodit&lt;/p&gt;
&lt;p&gt;### Summary
jodit&amp;#39;s built-in `clean-html` sanitizer can be bypassed by a MathML/`&amp;lt;style&amp;gt;` carrier that hides a dangerous element from the sanitizer&amp;#39;s element walk, so a no-interaction event handler survives into the editor value. When an application supplies attacker-influenced HTML to the editor&amp;#39;s value-set or insertion paths, the sanitized output still contains a live `&amp;lt;img ... onload=...&amp;gt;` (or another non-`onerror` handler such as `onfocus`). A consumer that renders that output (`element.innerHTML = editor.value`) executes the handler with no user interaction. This is a stored cross-site scripting vulnerability, confirmed live on the shipped `es2021/jodit.min.js` for 4.12.25 and the latest 4.12.27 (in Chromium via a client-side `innerHTML` consumer, and in Firefox via server-rendered / document-context output; see the cross-browser note under Proof of concept).&lt;/p&gt;
&lt;p&gt;### Details
The bypass exploits the order in which `clean-html` parses, walks, and re-serializes the value.&lt;/p&gt;
&lt;p&gt;1. On the value-set path, the `clean-html` plugin handles `:beforeSetNativeEditorValue` (`src/plugins/clean-html/clean-html.ts:116`), parsing the value into an inert document: `sandBox.innerHTML = data.value`.&lt;/p&gt;
&lt;p&gt;2. In that parse, the source nesting `math &amp;gt; mtext &amp;gt; table &amp;gt; mglyph &amp;gt; style` triggers MathML text-integration-point and foster-parenting rules: the `&amp;lt;img&amp;gt;` is parsed as text inside `&amp;lt;style&amp;gt;` (rawtext), not as an element. The `&amp;lt;table&amp;gt;` is foster-parented out, and the `&amp;lt;mglyph&amp;gt;` MathML text-integration…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: jodit&lt;/p&gt;
&lt;p&gt;### Summary
jodit&amp;#39;s built-in `clean-html` sanitizer can be bypassed by a MathML/`&amp;lt;style&amp;gt;` carrier that hides a dangerous element from the sanitizer&amp;#39;s element walk, so a no-interaction event handler survives into the editor value. When an application supplies attacker-influenced HTML to the editor&amp;#39;s value-set or insertion paths, the sanitized output still contains a live `&amp;lt;img ... onload=...&amp;gt;` (or another non-`onerror` handler such as `onfocus`). A consumer that renders that output (`element.innerHTML = editor.value`) executes the handler with no user interaction. This is a stored cross-site scripting vulnerability, confirmed live on the shipped `es2021/jodit.min.js` for 4.12.25 and the latest 4.12.27 (in Chromium via a client-side `innerHTML` consumer, and in Firefox via server-rendered / document-context output; see the cross-browser note under Proof of concept).&lt;/p&gt;
&lt;p&gt;### Details
The bypass exploits the order in which `clean-html` parses, walks, and re-serializes the value.&lt;/p&gt;
&lt;p&gt;1. On the value-set path, the `clean-html` plugin handles `:beforeSetNativeEditorValue` (`src/plugins/clean-html/clean-html.ts:116`), parsing the value into an inert document: `sandBox.innerHTML = data.value`.&lt;/p&gt;
&lt;p&gt;2. In that parse, the source nesting `math &amp;gt; mtext &amp;gt; table &amp;gt; mglyph &amp;gt; style` triggers MathML text-integration-point and foster-parenting rules: the `&amp;lt;img&amp;gt;` is parsed as text inside `&amp;lt;style&amp;gt;` (rawtext), not as an element. The `&amp;lt;table&amp;gt;` is foster-parented out, and the `&amp;lt;mglyph&amp;gt;` MathML text-integration…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rxcw-mc6f-6hr3</guid>
    </item>
  </channel>
</rss>
