<?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 10:53:17 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-289365</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-289365</link>
      <description>EUVD-2026-289365</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-289365</guid>
    </item>
    <item>
      <title>fkie_cve-2025-12002</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-12002</link>
      <description>&lt;p&gt;The Feeds for YouTube Pro plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 2.6.0 via the &amp;#39;sby_check_wp_submit&amp;#39; AJAX action. This is due to insufficient sanitization of user-supplied data and the use of that data in a file operation. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information, granted the &amp;#39;Save Featured Images&amp;#39; setting is enabled and &amp;#39;Disable WP Posts&amp;#39; is disabled. Note: This vulnerability only affects the Pro version of Feeds for YouTube.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Feeds for YouTube Pro plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 2.6.0 via the &amp;#39;sby_check_wp_submit&amp;#39; AJAX action. This is due to insufficient sanitization of user-supplied data and the use of that data in a file operation. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information, granted the &amp;#39;Save Featured Images&amp;#39; setting is enabled and &amp;#39;Disable WP Posts&amp;#39; is disabled. Note: This vulnerability only affects the Pro version of Feeds for YouTube.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-12002</guid>
    </item>
    <item>
      <title>GHSA-m78r-r2pf-69wj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m78r-r2pf-69wj</link>
      <description>&lt;p&gt;The Feeds for YouTube Pro plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 2.6.0 via the &amp;#39;sby_check_wp_submit&amp;#39; AJAX action. This is due to insufficient sanitization of user-supplied data and the use of that data in a file operation. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information, granted the &amp;#39;Save Featured Images&amp;#39; setting is enabled and &amp;#39;Disable WP Posts&amp;#39; is disabled. Note: This vulnerability only affects the Pro version of Feeds for YouTube.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Feeds for YouTube Pro plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 2.6.0 via the &amp;#39;sby_check_wp_submit&amp;#39; AJAX action. This is due to insufficient sanitization of user-supplied data and the use of that data in a file operation. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information, granted the &amp;#39;Save Featured Images&amp;#39; setting is enabled and &amp;#39;Disable WP Posts&amp;#39; is disabled. Note: This vulnerability only affects the Pro version of Feeds for YouTube.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m78r-r2pf-69wj</guid>
    </item>
  </channel>
</rss>
