<?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 10:30:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-355182</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-355182</link>
      <description>EUVD-2026-355182</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-355182</guid>
    </item>
    <item>
      <title>fkie_cve-2026-17582</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-17582</link>
      <description>&lt;p&gt;The Slider Hero plugin for WordPress is vulnerable to second-order SQL Injection in versions up to, and including, 9.1.7 via the qcld_sliderhero_duplicate() function. Slide data (description, title, btn, btn2, image_link, custom, etc.) is stored safely via $wpdb-&amp;gt;update() with %s placeholders in the qchero_save_image AJAX handler, but when an administrator triggers the &amp;#39;heroduplicateslider&amp;#39; task, qcld_sliderhero_duplicate() re-reads every slide column and concatenates the raw values directly into an INSERT VALUES tuple that is then executed with $wpdb-&amp;gt;query() — with no $wpdb-&amp;gt;prepare(), esc_sql(), or _real_escape_string in between. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Slider Hero plugin for WordPress is vulnerable to second-order SQL Injection in versions up to, and including, 9.1.7 via the qcld_sliderhero_duplicate() function. Slide data (description, title, btn, btn2, image_link, custom, etc.) is stored safely via $wpdb-&amp;gt;update() with %s placeholders in the qchero_save_image AJAX handler, but when an administrator triggers the &amp;#39;heroduplicateslider&amp;#39; task, qcld_sliderhero_duplicate() re-reads every slide column and concatenates the raw values directly into an INSERT VALUES tuple that is then executed with $wpdb-&amp;gt;query() — with no $wpdb-&amp;gt;prepare(), esc_sql(), or _real_escape_string in between. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-17582</guid>
    </item>
    <item>
      <title>GHSA-vxq7-r2mm-g784</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vxq7-r2mm-g784</link>
      <description>&lt;p&gt;The Slider Hero plugin for WordPress is vulnerable to second-order SQL Injection in versions up to, and including, 9.1.7 via the qcld_sliderhero_duplicate() function. Slide data (description, title, btn, btn2, image_link, custom, etc.) is stored safely via $wpdb-&amp;gt;update() with %s placeholders in the qchero_save_image AJAX handler, but when an administrator triggers the &amp;#39;heroduplicateslider&amp;#39; task, qcld_sliderhero_duplicate() re-reads every slide column and concatenates the raw values directly into an INSERT VALUES tuple that is then executed with $wpdb-&amp;gt;query() — with no $wpdb-&amp;gt;prepare(), esc_sql(), or _real_escape_string in between. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Slider Hero plugin for WordPress is vulnerable to second-order SQL Injection in versions up to, and including, 9.1.7 via the qcld_sliderhero_duplicate() function. Slide data (description, title, btn, btn2, image_link, custom, etc.) is stored safely via $wpdb-&amp;gt;update() with %s placeholders in the qchero_save_image AJAX handler, but when an administrator triggers the &amp;#39;heroduplicateslider&amp;#39; task, qcld_sliderhero_duplicate() re-reads every slide column and concatenates the raw values directly into an INSERT VALUES tuple that is then executed with $wpdb-&amp;gt;query() — with no $wpdb-&amp;gt;prepare(), esc_sql(), or _real_escape_string in between. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vxq7-r2mm-g784</guid>
    </item>
  </channel>
</rss>
