<?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>Tue, 06 Oct 2026 06:04:12 +0000</lastBuildDate>
    <item>
      <title>cnvd-2019-46263</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2019-46263</link>
      <description>cnvd-2019-46263</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2019-46263</guid>
    </item>
    <item>
      <title>EUVD-2026-57930</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-57930</link>
      <description>EUVD-2026-57930</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-57930</guid>
    </item>
    <item>
      <title>fkie_cve-2019-16766</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2019-16766</link>
      <description>&lt;p&gt;When using wagtail-2fa before 1.3.0, if someone gains access to someone&amp;#39;s Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When using wagtail-2fa before 1.3.0, if someone gains access to someone&amp;#39;s Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2019-16766</guid>
    </item>
    <item>
      <title>GHSA-89px-ww3j-g2mm — 2FA bypass in Wagtail through new device path</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-89px-ww3j-g2mm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail-2fa&lt;/p&gt;
&lt;p&gt;## 2FA bypass through new device path&lt;/p&gt;
&lt;p&gt;### Impact
If someone gains access to someone&amp;#39;s Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS.&lt;/p&gt;
&lt;p&gt;### Patches
This problem has been patched in version 1.3.0.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no workaround at the moment.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa)
* Email us at [security@labdigital.nl](mailto:security@labdigital.nl)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail-2fa&lt;/p&gt;
&lt;p&gt;## 2FA bypass through new device path&lt;/p&gt;
&lt;p&gt;### Impact
If someone gains access to someone&amp;#39;s Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS.&lt;/p&gt;
&lt;p&gt;### Patches
This problem has been patched in version 1.3.0.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no workaround at the moment.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa)
* Email us at [security@labdigital.nl](mailto:security@labdigital.nl)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-89px-ww3j-g2mm</guid>
    </item>
    <item>
      <title>gsd-2019-16766</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2019-16766</link>
      <description>gsd-2019-16766</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2019-16766</guid>
    </item>
    <item>
      <title>PYSEC-2019-135</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2019-135</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail-2fa&lt;/p&gt;
&lt;p&gt;When using wagtail-2fa before 1.3.0, if someone gains access to someone&amp;#39;s Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail-2fa&lt;/p&gt;
&lt;p&gt;When using wagtail-2fa before 1.3.0, if someone gains access to someone&amp;#39;s Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2019-135</guid>
    </item>
  </channel>
</rss>
