<?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>Wed, 21 Oct 2026 21:42:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-26332</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-26332</link>
      <description>EUVD-2026-26332</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-26332</guid>
    </item>
    <item>
      <title>fkie_cve-2021-29434</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-29434</link>
      <description>&lt;p&gt;Wagtail is a Django content management system. In affected versions of Wagtail, when saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. See referenced GitHub advisory for additional details, including a workaround. Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Wagtail is a Django content management system. In affected versions of Wagtail, when saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. See referenced GitHub advisory for additional details, including a workaround. Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-29434</guid>
    </item>
    <item>
      <title>GHSA-wq5h-f9p5-q7fx — Improper validation of URLs ('Cross-site Scripting') in Wagtail rich text fields</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wq5h-f9p5-q7fx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;### Impact
When saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).&lt;/p&gt;
&lt;p&gt;### Workarounds
For sites that cannot easily upgrade to a current supported version, the vulnerability can be patched by adding the following code to a `wagtail_hooks.py` module in any installed app:&lt;/p&gt;
&lt;p&gt;```python
from draftjs_exporter.dom import DOM
from wagtail.admin.rich_text.converters.html_to_contentstate import ExternalLinkElementHandler, PageLinkElementHandler
from wagtail.core import hooks
from wagtail.core.whitelist import check_url&lt;/p&gt;
&lt;p&gt;def link_entity(props):
    id_ = props.get(&amp;#39;id&amp;#39;)
    link_props = {}&lt;/p&gt;
&lt;p&gt;if id_ is not None:
        link_props[&amp;#39;linktype&amp;#39;] = &amp;#39;page&amp;#39;
        link_props[&amp;#39;id&amp;#39;] = id_
    else:
        link_props[&amp;#39;href&amp;#39;] = check_url(props.get(&amp;#39;url&amp;#39;))&lt;/p&gt;
&lt;p&gt;return DOM.create_element(&amp;#39;a&amp;#39;, link_props, props[&amp;#39;children&amp;#39;])&lt;/p&gt;
&lt;p&gt;@hooks.register(&amp;#39;register_rich_text_features&amp;#39;, order=1)
def register_link(features):
    features.register_converter_rule(&amp;#39;contentstate&amp;#39;, &amp;#39;link&amp;#39;, {
        &amp;#39;from_database_format&amp;#39;: {…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;### Impact
When saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).&lt;/p&gt;
&lt;p&gt;### Workarounds
For sites that cannot easily upgrade to a current supported version, the vulnerability can be patched by adding the following code to a `wagtail_hooks.py` module in any installed app:&lt;/p&gt;
&lt;p&gt;```python
from draftjs_exporter.dom import DOM
from wagtail.admin.rich_text.converters.html_to_contentstate import ExternalLinkElementHandler, PageLinkElementHandler
from wagtail.core import hooks
from wagtail.core.whitelist import check_url&lt;/p&gt;
&lt;p&gt;def link_entity(props):
    id_ = props.get(&amp;#39;id&amp;#39;)
    link_props = {}&lt;/p&gt;
&lt;p&gt;if id_ is not None:
        link_props[&amp;#39;linktype&amp;#39;] = &amp;#39;page&amp;#39;
        link_props[&amp;#39;id&amp;#39;] = id_
    else:
        link_props[&amp;#39;href&amp;#39;] = check_url(props.get(&amp;#39;url&amp;#39;))&lt;/p&gt;
&lt;p&gt;return DOM.create_element(&amp;#39;a&amp;#39;, link_props, props[&amp;#39;children&amp;#39;])&lt;/p&gt;
&lt;p&gt;@hooks.register(&amp;#39;register_rich_text_features&amp;#39;, order=1)
def register_link(features):
    features.register_converter_rule(&amp;#39;contentstate&amp;#39;, &amp;#39;link&amp;#39;, {
        &amp;#39;from_database_format&amp;#39;: {…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wq5h-f9p5-q7fx</guid>
    </item>
    <item>
      <title>gsd-2021-29434</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-29434</link>
      <description>gsd-2021-29434</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-29434</guid>
    </item>
    <item>
      <title>PYSEC-2021-114</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2021-114</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;Wagtail is a Django content management system. In affected versions of Wagtail, when saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. See referenced GitHub advisory for additional details, including a workaround. Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;Wagtail is a Django content management system. In affected versions of Wagtail, when saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. See referenced GitHub advisory for additional details, including a workaround. Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2021-114</guid>
    </item>
  </channel>
</rss>
