<?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>Mon, 05 Oct 2026 12:34:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-308175</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-308175</link>
      <description>EUVD-2026-308175</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-308175</guid>
    </item>
    <item>
      <title>fkie_cve-2026-7567</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-7567</link>
      <description>&lt;p&gt;The Temporary Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.0.0. This is due to improper input validation in the maybe_login_temporary_user() function, which fails to verify that the &amp;#39;temp-login-token&amp;#39; GET parameter is a scalar string before processing it. When the parameter is supplied as an array, PHP&amp;#39;s empty() check is bypassed and sanitize_key() returns an empty string, which is then passed as the meta_value to get_users(). WordPress ignores an empty meta_value and returns all users matching the meta_key &amp;#39;_temporary_login_token&amp;#39;, allowing authentication without a valid token. This makes it possible for unauthenticated attackers to authenticate as any active temporary login user by sending a single crafted GET request.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Temporary Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.0.0. This is due to improper input validation in the maybe_login_temporary_user() function, which fails to verify that the &amp;#39;temp-login-token&amp;#39; GET parameter is a scalar string before processing it. When the parameter is supplied as an array, PHP&amp;#39;s empty() check is bypassed and sanitize_key() returns an empty string, which is then passed as the meta_value to get_users(). WordPress ignores an empty meta_value and returns all users matching the meta_key &amp;#39;_temporary_login_token&amp;#39;, allowing authentication without a valid token. This makes it possible for unauthenticated attackers to authenticate as any active temporary login user by sending a single crafted GET request.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-7567</guid>
    </item>
    <item>
      <title>GHSA-4v98-7r2c-mxg7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4v98-7r2c-mxg7</link>
      <description>&lt;p&gt;The Temporary Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.0.0. This is due to improper input validation in the maybe_login_temporary_user() function, which fails to verify that the &amp;#39;temp-login-token&amp;#39; GET parameter is a scalar string before processing it. When the parameter is supplied as an array, PHP&amp;#39;s empty() check is bypassed and sanitize_key() returns an empty string, which is then passed as the meta_value to get_users(). WordPress ignores an empty meta_value and returns all users matching the meta_key &amp;#39;_temporary_login_token&amp;#39;, allowing authentication without a valid token. This makes it possible for unauthenticated attackers to authenticate as any active temporary login user by sending a single crafted GET request.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Temporary Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.0.0. This is due to improper input validation in the maybe_login_temporary_user() function, which fails to verify that the &amp;#39;temp-login-token&amp;#39; GET parameter is a scalar string before processing it. When the parameter is supplied as an array, PHP&amp;#39;s empty() check is bypassed and sanitize_key() returns an empty string, which is then passed as the meta_value to get_users(). WordPress ignores an empty meta_value and returns all users matching the meta_key &amp;#39;_temporary_login_token&amp;#39;, allowing authentication without a valid token. This makes it possible for unauthenticated attackers to authenticate as any active temporary login user by sending a single crafted GET request.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4v98-7r2c-mxg7</guid>
    </item>
  </channel>
</rss>
