<?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>Sat, 03 Oct 2026 18:25:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-267430</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-267430</link>
      <description>EUVD-2026-267430</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-267430</guid>
    </item>
    <item>
      <title>fkie_cve-2026-25517</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-25517</link>
      <description>&lt;p&gt;Wagtail is an open source content management system built on Django. Prior to versions 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3, due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model&amp;#39;s fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user&amp;#39;s choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. This issue has been patched in versions 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Wagtail is an open source content management system built on Django. Prior to versions 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3, due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model&amp;#39;s fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user&amp;#39;s choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. This issue has been patched in versions 6.3.6, 7.0.4, 7.1.3, 7.2.2, and 7.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-25517</guid>
    </item>
    <item>
      <title>GHSA-4qvv-g3vr-m348 — Wagtail has improper permission handling on admin preview endpoints</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4qvv-g3vr-m348</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;### Impact
Due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model&amp;#39;s fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user&amp;#39;s choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. 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 6.3.6, 7.0.4, 7.1.3 and 7.2.2. The new 7.3 feature release also incorporates this fix.&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround is available.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;Many thanks to @thxtech for reporting this issue.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;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.io/en/stable/support.html)
- Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view our [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
Due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model&amp;#39;s fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user&amp;#39;s choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. 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 6.3.6, 7.0.4, 7.1.3 and 7.2.2. The new 7.3 feature release also incorporates this fix.&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround is available.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;Many thanks to @thxtech for reporting this issue.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;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.io/en/stable/support.html)
- Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view our [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-4qvv-g3vr-m348</guid>
    </item>
    <item>
      <title>PYSEC-2026-2030 — Wagtail has improper permission handling on admin preview endpoints</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2030</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;### Impact
Due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model&amp;#39;s fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user&amp;#39;s choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. 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 6.3.6, 7.0.4, 7.1.3 and 7.2.2. The new 7.3 feature release also incorporates this fix.&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround is available.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;Many thanks to @thxtech for reporting this issue.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;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.io/en/stable/support.html)
- Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view our [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
Due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model&amp;#39;s fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user&amp;#39;s choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. 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 6.3.6, 7.0.4, 7.1.3 and 7.2.2. The new 7.3 feature release also incorporates this fix.&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround is available.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;Many thanks to @thxtech for reporting this issue.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;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.io/en/stable/support.html)
- Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view our [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/pysec-2026-2030</guid>
    </item>
  </channel>
</rss>
