<?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>Thu, 08 Oct 2026 20:23:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-289418</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-289418</link>
      <description>EUVD-2026-289418</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-289418</guid>
    </item>
    <item>
      <title>fkie_cve-2024-4185</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-4185</link>
      <description>&lt;p&gt;The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Email Verification and Authentication Bypass in all versions up to, and including, 2.7.4 via the use of insufficiently random activation code. This makes it possible for unauthenticated attackers to bypass the email verification, and if both the &amp;#34;Login the user automatically after the account is verified&amp;#34; and &amp;#34;Verify account for current users&amp;#34; options are checked, then it potentially makes it possible for attackers to bypass authentication for other users.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Email Verification and Authentication Bypass in all versions up to, and including, 2.7.4 via the use of insufficiently random activation code. This makes it possible for unauthenticated attackers to bypass the email verification, and if both the &amp;#34;Login the user automatically after the account is verified&amp;#34; and &amp;#34;Verify account for current users&amp;#34; options are checked, then it potentially makes it possible for attackers to bypass authentication for other users.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-4185</guid>
    </item>
    <item>
      <title>GHSA-7fhm-gx9f-8c93</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7fhm-gx9f-8c93</link>
      <description>&lt;p&gt;The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Email Verification and Authentication Bypass in all versions up to, and including, 2.7.4 via the use of insufficiently random activation code. This makes it possible for unauthenticated attackers to bypass the email verification, and if both the &amp;#34;Login the user automatically after the account is verified&amp;#34; and &amp;#34;Verify account for current users&amp;#34; options are checked, then it potentially makes it possible for attackers to bypass authentication for other users.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Email Verification and Authentication Bypass in all versions up to, and including, 2.7.4 via the use of insufficiently random activation code. This makes it possible for unauthenticated attackers to bypass the email verification, and if both the &amp;#34;Login the user automatically after the account is verified&amp;#34; and &amp;#34;Verify account for current users&amp;#34; options are checked, then it potentially makes it possible for attackers to bypass authentication for other users.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7fhm-gx9f-8c93</guid>
    </item>
    <item>
      <title>gsd-2024-4185</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-4185</link>
      <description>gsd-2024-4185</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-4185</guid>
    </item>
  </channel>
</rss>
