<?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 09:18:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-320057</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320057</link>
      <description>EUVD-2026-320057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320057</guid>
    </item>
    <item>
      <title>fkie_cve-2026-3481</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-3481</link>
      <description>&lt;p&gt;The WP Blockade plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the &amp;#39;shortcode&amp;#39; parameter in all versions up to and including 0.9.14. This is due to insufficient input sanitization and output escaping in the render_shortcode_preview() function. The function receives user input from $_GET[&amp;#39;shortcode&amp;#39;], passes it through stripslashes() without any sanitization, and then outputs it directly via echo do_shortcode($shortcode) on line 393. When the input is not a valid WordPress shortcode (e.g., an HTML tag with JavaScript event handlers), do_shortcode() returns it unchanged, and it is reflected into the page without escaping. The endpoint is registered via admin_post_ (not admin_post_nopriv_), meaning it requires the user to be logged in with at minimum a Subscriber-level account. There is no nonce verification or additional capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute if they can successfully trick a user into performing an action such as clicking a link.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Blockade plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the &amp;#39;shortcode&amp;#39; parameter in all versions up to and including 0.9.14. This is due to insufficient input sanitization and output escaping in the render_shortcode_preview() function. The function receives user input from $_GET[&amp;#39;shortcode&amp;#39;], passes it through stripslashes() without any sanitization, and then outputs it directly via echo do_shortcode($shortcode) on line 393. When the input is not a valid WordPress shortcode (e.g., an HTML tag with JavaScript event handlers), do_shortcode() returns it unchanged, and it is reflected into the page without escaping. The endpoint is registered via admin_post_ (not admin_post_nopriv_), meaning it requires the user to be logged in with at minimum a Subscriber-level account. There is no nonce verification or additional capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute if they can successfully trick a user into performing an action such as clicking a link.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-3481</guid>
    </item>
    <item>
      <title>GHSA-p9mp-xq3w-289v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p9mp-xq3w-289v</link>
      <description>&lt;p&gt;The WP Blockade plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the &amp;#39;shortcode&amp;#39; parameter in all versions up to and including 0.9.14. This is due to insufficient input sanitization and output escaping in the render_shortcode_preview() function. The function receives user input from $_GET[&amp;#39;shortcode&amp;#39;], passes it through stripslashes() without any sanitization, and then outputs it directly via echo do_shortcode($shortcode) on line 393. When the input is not a valid WordPress shortcode (e.g., an HTML tag with JavaScript event handlers), do_shortcode() returns it unchanged, and it is reflected into the page without escaping. The endpoint is registered via admin_post_ (not admin_post_nopriv_), meaning it requires the user to be logged in with at minimum a Subscriber-level account. There is no nonce verification or additional capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute if they can successfully trick a user into performing an action such as clicking a link.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Blockade plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the &amp;#39;shortcode&amp;#39; parameter in all versions up to and including 0.9.14. This is due to insufficient input sanitization and output escaping in the render_shortcode_preview() function. The function receives user input from $_GET[&amp;#39;shortcode&amp;#39;], passes it through stripslashes() without any sanitization, and then outputs it directly via echo do_shortcode($shortcode) on line 393. When the input is not a valid WordPress shortcode (e.g., an HTML tag with JavaScript event handlers), do_shortcode() returns it unchanged, and it is reflected into the page without escaping. The endpoint is registered via admin_post_ (not admin_post_nopriv_), meaning it requires the user to be logged in with at minimum a Subscriber-level account. There is no nonce verification or additional capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute if they can successfully trick a user into performing an action such as clicking a link.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p9mp-xq3w-289v</guid>
    </item>
  </channel>
</rss>
