<?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 00:41:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-324167</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-324167</link>
      <description>EUVD-2026-324167</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-324167</guid>
    </item>
    <item>
      <title>fkie_cve-2026-5073</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5073</link>
      <description>&lt;p&gt;The ARMember Premium plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order&amp;#39; parameter of the &amp;#39;arm_directory_paging_action&amp;#39; AJAX action in all versions up to, and including, 7.3.1. This is due to insufficient escaping on the user-supplied &amp;#39;order&amp;#39; and &amp;#39;orderby&amp;#39; parameters and the lack of sufficient preparation on the existing SQL query in the `arm_get_directory_members()` function. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The ARMember Premium plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order&amp;#39; parameter of the &amp;#39;arm_directory_paging_action&amp;#39; AJAX action in all versions up to, and including, 7.3.1. This is due to insufficient escaping on the user-supplied &amp;#39;order&amp;#39; and &amp;#39;orderby&amp;#39; parameters and the lack of sufficient preparation on the existing SQL query in the `arm_get_directory_members()` function. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-5073</guid>
    </item>
    <item>
      <title>GHSA-p4qm-892g-4gm7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p4qm-892g-4gm7</link>
      <description>&lt;p&gt;The ARMember Premium plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order&amp;#39; parameter of the &amp;#39;arm_directory_paging_action&amp;#39; AJAX action in all versions up to, and including, 7.3.1. This is due to insufficient escaping on the user-supplied &amp;#39;order&amp;#39; and &amp;#39;orderby&amp;#39; parameters and the lack of sufficient preparation on the existing SQL query in the `arm_get_directory_members()` function. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The ARMember Premium plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order&amp;#39; parameter of the &amp;#39;arm_directory_paging_action&amp;#39; AJAX action in all versions up to, and including, 7.3.1. This is due to insufficient escaping on the user-supplied &amp;#39;order&amp;#39; and &amp;#39;orderby&amp;#39; parameters and the lack of sufficient preparation on the existing SQL query in the `arm_get_directory_members()` function. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p4qm-892g-4gm7</guid>
    </item>
  </channel>
</rss>
