<?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>Wed, 07 Oct 2026 18:30:01 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-283774</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-283774</link>
      <description>EUVD-2026-283774</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-283774</guid>
    </item>
    <item>
      <title>fkie_cve-2026-3629</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-3629</link>
      <description>&lt;p&gt;The Import and export users and customers plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.29.7. This is due to the &amp;#39;save_extra_user_profile_fields&amp;#39; function not properly restricting which user meta keys can be updated via profile fields. The &amp;#39;get_restricted_fields&amp;#39; method does not include sensitive meta keys such as &amp;#39;wp_capabilities&amp;#39;. This makes it possible for unauthenticated attackers to escalate their privileges to Administrator by submitting a crafted registration request that sets the &amp;#39;wp_capabilities&amp;#39; meta key. The vulnerability can only be exploited if the &amp;#34;Show fields in profile&amp;#34; setting is enabled and a CSV with a wp_capabilities column header has been previously imported.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Import and export users and customers plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.29.7. This is due to the &amp;#39;save_extra_user_profile_fields&amp;#39; function not properly restricting which user meta keys can be updated via profile fields. The &amp;#39;get_restricted_fields&amp;#39; method does not include sensitive meta keys such as &amp;#39;wp_capabilities&amp;#39;. This makes it possible for unauthenticated attackers to escalate their privileges to Administrator by submitting a crafted registration request that sets the &amp;#39;wp_capabilities&amp;#39; meta key. The vulnerability can only be exploited if the &amp;#34;Show fields in profile&amp;#34; setting is enabled and a CSV with a wp_capabilities column header has been previously imported.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-3629</guid>
    </item>
    <item>
      <title>GHSA-974q-2m48-3288</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-974q-2m48-3288</link>
      <description>&lt;p&gt;The Import and export users and customers plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.29.7. This is due to the &amp;#39;save_extra_user_profile_fields&amp;#39; function not properly restricting which user meta keys can be updated via profile fields. The &amp;#39;get_restricted_fields&amp;#39; method does not include sensitive meta keys such as &amp;#39;wp_capabilities&amp;#39;. This makes it possible for unauthenticated attackers to escalate their privileges to Administrator by submitting a crafted registration request that sets the &amp;#39;wp_capabilities&amp;#39; meta key. The vulnerability can only be exploited if the &amp;#34;Show fields in profile&amp;#34; setting is enabled and a CSV with a wp_capabilities column header has been previously imported.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Import and export users and customers plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.29.7. This is due to the &amp;#39;save_extra_user_profile_fields&amp;#39; function not properly restricting which user meta keys can be updated via profile fields. The &amp;#39;get_restricted_fields&amp;#39; method does not include sensitive meta keys such as &amp;#39;wp_capabilities&amp;#39;. This makes it possible for unauthenticated attackers to escalate their privileges to Administrator by submitting a crafted registration request that sets the &amp;#39;wp_capabilities&amp;#39; meta key. The vulnerability can only be exploited if the &amp;#34;Show fields in profile&amp;#34; setting is enabled and a CSV with a wp_capabilities column header has been previously imported.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-974q-2m48-3288</guid>
    </item>
  </channel>
</rss>
