<?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, 17 Nov 2026 04:28:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-406075</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-406075</link>
      <description>EUVD-2026-406075</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-406075</guid>
    </item>
    <item>
      <title>GHSA-vf5h-4472-f6g2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vf5h-4472-f6g2</link>
      <description>&lt;p&gt;The Recipe Card Blocks Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;steps[].text&amp;#39; parameter in all versions up to, and including, 3.7.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because wp_kses_post() preserves block-delimiter HTML comments verbatim on save, a Contributor can embed event-handler payloads inside the block&amp;#39;s steps[].text attribute in a draft or pending post without the unfiltered_html capability, and the payload executes for any visitor — including privileged editors and administrators who preview or publish the post — as well as through the public print endpoint.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Recipe Card Blocks Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;steps[].text&amp;#39; parameter in all versions up to, and including, 3.7.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because wp_kses_post() preserves block-delimiter HTML comments verbatim on save, a Contributor can embed event-handler payloads inside the block&amp;#39;s steps[].text attribute in a draft or pending post without the unfiltered_html capability, and the payload executes for any visitor — including privileged editors and administrators who preview or publish the post — as well as through the public print endpoint.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vf5h-4472-f6g2</guid>
    </item>
  </channel>
</rss>
