<?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>Sun, 04 Oct 2026 22:21:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-309941</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309941</link>
      <description>EUVD-2026-309941</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309941</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44198</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44198</link>
      <description>&lt;p&gt;Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could still access the history report for the page, potentially resulting in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could still access the history report for the page, potentially resulting in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44198</guid>
    </item>
    <item>
      <title>GHSA-c4mr-889m-vgf6 — Wagtail has improper permission handling when viewing page history</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c4mr-889m-vgf6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A CMS user without the ability to edit a page could still access the history report for the page, potentially resulting in disclosure of sensitive information.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions have been released as Wagtail 7.0.7 and 7.3.2. The new 7.4 LTS feature release also incorporates this fix.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No workaround is available.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;Wagtail thanks Seoyoung Kang @seoyoung-kang who is from AhnLab and also an independent security researcher for reporting this issue.&lt;/p&gt;
&lt;p&gt;### For more information
If there are any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* Visit Wagtail&amp;#39;s [support channels](https://docs.wagtail.org/en/stable/support.html)
* Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view the [security policy](https://github.com/wagtail/wagtail/security/policy) for more information).&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&lt;/p&gt;
&lt;p&gt;A CMS user without the ability to edit a page could still access the history report for the page, potentially resulting in disclosure of sensitive information.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions have been released as Wagtail 7.0.7 and 7.3.2. The new 7.4 LTS feature release also incorporates this fix.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No workaround is available.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;Wagtail thanks Seoyoung Kang @seoyoung-kang who is from AhnLab and also an independent security researcher for reporting this issue.&lt;/p&gt;
&lt;p&gt;### For more information
If there are any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* Visit Wagtail&amp;#39;s [support channels](https://docs.wagtail.org/en/stable/support.html)
* Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view the [security policy](https://github.com/wagtail/wagtail/security/policy) for more information).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c4mr-889m-vgf6</guid>
    </item>
    <item>
      <title>PYSEC-2026-147</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-147</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could still access the history report for the page, potentially resulting in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.&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 an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could still access the history report for the page, potentially resulting in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-147</guid>
    </item>
  </channel>
</rss>
