<?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 22:23:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-285205</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-285205</link>
      <description>EUVD-2026-285205</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-285205</guid>
    </item>
    <item>
      <title>fkie_cve-2026-3460</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-3460</link>
      <description>&lt;p&gt;The REST API TO MiniProgram plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.2. This is due to the permission callback (update_user_wechatshop_info_permissions_check) only validating that the supplied &amp;#39;openid&amp;#39; parameter corresponds to an existing WordPress user, while the callback function (update_user_wechatshop_info) uses a separate, attacker-controlled &amp;#39;userid&amp;#39; parameter to determine which user&amp;#39;s metadata gets modified, with no verification that the &amp;#39;openid&amp;#39; and &amp;#39;userid&amp;#39; belong to the same user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify arbitrary users&amp;#39; store-related metadata (storeinfo, storeappid, storename) via the &amp;#39;userid&amp;#39; REST API parameter.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The REST API TO MiniProgram plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.2. This is due to the permission callback (update_user_wechatshop_info_permissions_check) only validating that the supplied &amp;#39;openid&amp;#39; parameter corresponds to an existing WordPress user, while the callback function (update_user_wechatshop_info) uses a separate, attacker-controlled &amp;#39;userid&amp;#39; parameter to determine which user&amp;#39;s metadata gets modified, with no verification that the &amp;#39;openid&amp;#39; and &amp;#39;userid&amp;#39; belong to the same user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify arbitrary users&amp;#39; store-related metadata (storeinfo, storeappid, storename) via the &amp;#39;userid&amp;#39; REST API parameter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-3460</guid>
    </item>
    <item>
      <title>GHSA-xxxv-phx4-9pvx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xxxv-phx4-9pvx</link>
      <description>&lt;p&gt;The REST API TO MiniProgram plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.2. This is due to the permission callback (update_user_wechatshop_info_permissions_check) only validating that the supplied &amp;#39;openid&amp;#39; parameter corresponds to an existing WordPress user, while the callback function (update_user_wechatshop_info) uses a separate, attacker-controlled &amp;#39;userid&amp;#39; parameter to determine which user&amp;#39;s metadata gets modified, with no verification that the &amp;#39;openid&amp;#39; and &amp;#39;userid&amp;#39; belong to the same user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify arbitrary users&amp;#39; store-related metadata (storeinfo, storeappid, storename) via the &amp;#39;userid&amp;#39; REST API parameter.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The REST API TO MiniProgram plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.2. This is due to the permission callback (update_user_wechatshop_info_permissions_check) only validating that the supplied &amp;#39;openid&amp;#39; parameter corresponds to an existing WordPress user, while the callback function (update_user_wechatshop_info) uses a separate, attacker-controlled &amp;#39;userid&amp;#39; parameter to determine which user&amp;#39;s metadata gets modified, with no verification that the &amp;#39;openid&amp;#39; and &amp;#39;userid&amp;#39; belong to the same user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify arbitrary users&amp;#39; store-related metadata (storeinfo, storeappid, storename) via the &amp;#39;userid&amp;#39; REST API parameter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xxxv-phx4-9pvx</guid>
    </item>
  </channel>
</rss>
