<?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 15:18:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-286655</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-286655</link>
      <description>EUVD-2026-286655</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-286655</guid>
    </item>
    <item>
      <title>fkie_cve-2025-13320</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-13320</link>
      <description>&lt;p&gt;The WP User Manager plugin for WordPress is vulnerable to Arbitrary File Deletion in all versions up to, and including, 2.9.12. This is due to insufficient validation of user-supplied file paths in the profile update functionality combined with improper handling of array inputs by PHP&amp;#39;s filter_input() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server via the &amp;#39;current_user_avatar&amp;#39; parameter in a two-stage attack which can make remote code execution possible. This only affects sites with the custom avatar setting enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP User Manager plugin for WordPress is vulnerable to Arbitrary File Deletion in all versions up to, and including, 2.9.12. This is due to insufficient validation of user-supplied file paths in the profile update functionality combined with improper handling of array inputs by PHP&amp;#39;s filter_input() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server via the &amp;#39;current_user_avatar&amp;#39; parameter in a two-stage attack which can make remote code execution possible. This only affects sites with the custom avatar setting enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-13320</guid>
    </item>
    <item>
      <title>GHSA-3h64-fx5v-2f3q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3h64-fx5v-2f3q</link>
      <description>&lt;p&gt;The WP User Manager plugin for WordPress is vulnerable to Arbitrary File Deletion in all versions up to, and including, 2.9.12. This is due to insufficient validation of user-supplied file paths in the profile update functionality combined with improper handling of array inputs by PHP&amp;#39;s filter_input() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server via the &amp;#39;current_user_avatar&amp;#39; parameter in a two-stage attack which can make remote code execution possible. This only affects sites with the custom avatar setting enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP User Manager plugin for WordPress is vulnerable to Arbitrary File Deletion in all versions up to, and including, 2.9.12. This is due to insufficient validation of user-supplied file paths in the profile update functionality combined with improper handling of array inputs by PHP&amp;#39;s filter_input() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server via the &amp;#39;current_user_avatar&amp;#39; parameter in a two-stage attack which can make remote code execution possible. This only affects sites with the custom avatar setting enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3h64-fx5v-2f3q</guid>
    </item>
  </channel>
</rss>
