<?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 14:39:01 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-287017</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-287017</link>
      <description>EUVD-2026-287017</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-287017</guid>
    </item>
    <item>
      <title>fkie_cve-2025-13539</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-13539</link>
      <description>&lt;p&gt;The FindAll Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.0.4. This is due to the plugin not properly logging in a user with the data that was previously verified through the &amp;#39;findall_membership_check_facebook_user&amp;#39; and the &amp;#39;findall_membership_check_google_user&amp;#39; functions. This makes it possible for unauthenticated attackers to log in as administrative users, as long as they have an existing account on the site which can easily be created by default through the temp user functionality, and access to the administrative user&amp;#39;s email.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The FindAll Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.0.4. This is due to the plugin not properly logging in a user with the data that was previously verified through the &amp;#39;findall_membership_check_facebook_user&amp;#39; and the &amp;#39;findall_membership_check_google_user&amp;#39; functions. This makes it possible for unauthenticated attackers to log in as administrative users, as long as they have an existing account on the site which can easily be created by default through the temp user functionality, and access to the administrative user&amp;#39;s email.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-13539</guid>
    </item>
    <item>
      <title>GHSA-pvpx-mqp7-546v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pvpx-mqp7-546v</link>
      <description>&lt;p&gt;The FindAll Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.0.4. This is due to the plugin not properly logging in a user with the data that was previously verified through the &amp;#39;findall_membership_check_facebook_user&amp;#39; and the &amp;#39;findall_membership_check_google_user&amp;#39; functions. This makes it possible for unauthenticated attackers to log in as administrative users, as long as they have an existing account on the site which can easily be created by default through the temp user functionality, and access to the administrative user&amp;#39;s email.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The FindAll Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.0.4. This is due to the plugin not properly logging in a user with the data that was previously verified through the &amp;#39;findall_membership_check_facebook_user&amp;#39; and the &amp;#39;findall_membership_check_google_user&amp;#39; functions. This makes it possible for unauthenticated attackers to log in as administrative users, as long as they have an existing account on the site which can easily be created by default through the temp user functionality, and access to the administrative user&amp;#39;s email.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pvpx-mqp7-546v</guid>
    </item>
  </channel>
</rss>
