<?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>Thu, 22 Oct 2026 01:32:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-194769</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-194769</link>
      <description>EUVD-2026-194769</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-194769</guid>
    </item>
    <item>
      <title>fkie_cve-2023-38500</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-38500</link>
      <description>&lt;p&gt;TYPO3 HTML Sanitizer is an HTML sanitizer, written in PHP, aiming to provide cross-site-scripting-safe markup based on explicitly allowed tags, attributes and values. Starting in version 1.0.0 and prior to versions 1.5.1 and 2.1.2, due to an encoding issue in the serialization layer, malicious markup nested in a `noscript` element was not encoded correctly. `noscript` is disabled in the default configuration, but might have been enabled in custom scenarios. This allows bypassing the cross-site scripting mechanism of TYPO3 HTML Sanitizer. Versions 1.5.1 and 2.1.2 fix the problem.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;TYPO3 HTML Sanitizer is an HTML sanitizer, written in PHP, aiming to provide cross-site-scripting-safe markup based on explicitly allowed tags, attributes and values. Starting in version 1.0.0 and prior to versions 1.5.1 and 2.1.2, due to an encoding issue in the serialization layer, malicious markup nested in a `noscript` element was not encoded correctly. `noscript` is disabled in the default configuration, but might have been enabled in custom scenarios. This allows bypassing the cross-site scripting mechanism of TYPO3 HTML Sanitizer. Versions 1.5.1 and 2.1.2 fix the problem.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-38500</guid>
    </item>
    <item>
      <title>GHSA-59jf-3q9v-rh6g — By-passing Cross-Site Scripting Protection in HTML Sanitizer</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-59jf-3q9v-rh6g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/html-sanitizer&lt;/p&gt;
&lt;p&gt;&amp;gt; ### CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C` (4.4)&lt;/p&gt;
&lt;p&gt;### Problem
Due to an encoding issue in the serialization layer, malicious markup nested in a `noscript` element was not encoded correctly. `noscript` is disabled in the default configuration, but might have been enabled in custom scenarios. This allows bypassing the cross-site scripting mechanism of [`typo3/html-sanitizer`](https://packagist.org/packages/typo3/html-sanitizer).&lt;/p&gt;
&lt;p&gt;### Solution
Update to `typo3/html-sanitizer` versions 1.5.1 or 2.1.2 that fix the problem described.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to David Klein and Yaniv Nizry who reported this issue, and to TYPO3 security team members Oliver Hader and Benjamin Franzke who fixed the issue.&lt;/p&gt;
&lt;p&gt;### References
* [TYPO3-CORE-SA-2023-002](https://typo3.org/security/advisory/typo3-core-sa-2023-002)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/html-sanitizer&lt;/p&gt;
&lt;p&gt;&amp;gt; ### CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C` (4.4)&lt;/p&gt;
&lt;p&gt;### Problem
Due to an encoding issue in the serialization layer, malicious markup nested in a `noscript` element was not encoded correctly. `noscript` is disabled in the default configuration, but might have been enabled in custom scenarios. This allows bypassing the cross-site scripting mechanism of [`typo3/html-sanitizer`](https://packagist.org/packages/typo3/html-sanitizer).&lt;/p&gt;
&lt;p&gt;### Solution
Update to `typo3/html-sanitizer` versions 1.5.1 or 2.1.2 that fix the problem described.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to David Klein and Yaniv Nizry who reported this issue, and to TYPO3 security team members Oliver Hader and Benjamin Franzke who fixed the issue.&lt;/p&gt;
&lt;p&gt;### References
* [TYPO3-CORE-SA-2023-002](https://typo3.org/security/advisory/typo3-core-sa-2023-002)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-59jf-3q9v-rh6g</guid>
    </item>
    <item>
      <title>gsd-2023-38500</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-38500</link>
      <description>gsd-2023-38500</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-38500</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-1878 — TYPO3 Core: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1878</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen oder Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen oder Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1878</guid>
    </item>
  </channel>
</rss>
