<?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://db.gcve.eu</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, 09 Nov 2026 17:53:49 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2023-41167</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2023-41167</link>
      <description>&lt;p&gt;@webiny/react-rich-text-renderer before 5.37.2 allows XSS attacks by content managers. This is a react component to render data coming from Webiny Headless CMS and Webiny Form Builder. Webiny is an open-source serverless enterprise CMS. The @webiny/react-rich-text-renderer package depends on the editor.js rich text editor to handle rich text content. The CMS stores rich text content from the editor.js into the database. When the @webiny/react-rich-text-renderer is used to render such content, it uses the dangerouslySetInnerHTML prop, without applying HTML sanitization. The issue arises when an actor, who in this context would specifically be a content manager with access to the CMS, inserts a malicious script as part of the user-defined input. This script is then injected and executed within the user&amp;#39;s browser when the main page or admin page loads.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@webiny/react-rich-text-renderer before 5.37.2 allows XSS attacks by content managers. This is a react component to render data coming from Webiny Headless CMS and Webiny Form Builder. Webiny is an open-source serverless enterprise CMS. The @webiny/react-rich-text-renderer package depends on the editor.js rich text editor to handle rich text content. The CMS stores rich text content from the editor.js into the database. When the @webiny/react-rich-text-renderer is used to render such content, it uses the dangerouslySetInnerHTML prop, without applying HTML sanitization. The issue arises when an actor, who in this context would specifically be a content manager with access to the CMS, inserts a malicious script as part of the user-defined input. This script is then injected and executed within the user&amp;#39;s browser when the main page or admin page loads.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2023-41167</guid>
    </item>
    <item>
      <title>GHSA-3x59-vrmc-5mx6 — @webiny/react-rich-text-renderer vulnerable to insecure rendering of rich text content</title>
      <link>https://db.gcve.eu/vuln/ghsa-3x59-vrmc-5mx6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @webiny/react-rich-text-renderer&lt;/p&gt;
&lt;p&gt;## Overview
`@webiny/react-rich-text-renderer` is a react component to render data coming from Webiny Headless CMS and Webiny Form Builder. The `@webiny/react-rich-text-renderer` package depends on the [editor.js](https://editorjs.io/) rich text editor to handle rich text content. The CMS stores rich text content from the `editor.js` into the database. When the `@webiny/react-rich-text-renderer` is used to render such content, it uses the `dangerouslySetInnerHTML` prop, without applying HTML sanitization. The issue arises when an actor, who in this context would specifically be a content manager with access to the CMS, inserts a malicious script as part of the user-defined input. This script is then injected and executed within the user&amp;#39;s browser when the main page or admin page loads.&lt;/p&gt;
&lt;p&gt;## Am I affected?
You will be affected if you&amp;#39;re running a Webiny project created prior to `5.35.0` and you&amp;#39;re using the legacy rich text editor (which uses `editor.js` library under the hood). If you&amp;#39;ve already switched to using the new rich text editor, powered by Lexical editor, you will not be affected by this.&lt;/p&gt;
&lt;p&gt;## How do I patch this vulnerability?
Update to Webiny version `5.37.2`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @webiny/react-rich-text-renderer&lt;/p&gt;
&lt;p&gt;## Overview
`@webiny/react-rich-text-renderer` is a react component to render data coming from Webiny Headless CMS and Webiny Form Builder. The `@webiny/react-rich-text-renderer` package depends on the [editor.js](https://editorjs.io/) rich text editor to handle rich text content. The CMS stores rich text content from the `editor.js` into the database. When the `@webiny/react-rich-text-renderer` is used to render such content, it uses the `dangerouslySetInnerHTML` prop, without applying HTML sanitization. The issue arises when an actor, who in this context would specifically be a content manager with access to the CMS, inserts a malicious script as part of the user-defined input. This script is then injected and executed within the user&amp;#39;s browser when the main page or admin page loads.&lt;/p&gt;
&lt;p&gt;## Am I affected?
You will be affected if you&amp;#39;re running a Webiny project created prior to `5.35.0` and you&amp;#39;re using the legacy rich text editor (which uses `editor.js` library under the hood). If you&amp;#39;ve already switched to using the new rich text editor, powered by Lexical editor, you will not be affected by this.&lt;/p&gt;
&lt;p&gt;## How do I patch this vulnerability?
Update to Webiny version `5.37.2`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-3x59-vrmc-5mx6</guid>
    </item>
    <item>
      <title>gsd-2023-41167</title>
      <link>https://db.gcve.eu/vuln/gsd-2023-41167</link>
      <description>gsd-2023-41167</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/gsd-2023-41167</guid>
    </item>
  </channel>
</rss>
