<?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 13:04:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2019-16766 — 2FA bypass in Wagtail through new device path</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2019-16766</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Lab Digital 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; Lab Digital 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/cve-2019-16766</guid>
    </item>
  </channel>
</rss>
