<?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>Mon, 05 Oct 2026 15:29:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-332414</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-332414</link>
      <description>EUVD-2026-332414</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-332414</guid>
    </item>
    <item>
      <title>fkie_cve-2026-7311</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-7311</link>
      <description>&lt;p&gt;The TinyPNG – JPEG, PNG &amp;amp; WebP image compression plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_converted_image_size function in all versions up to, and including, 3.6.13. This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). An attacker can exploit this by injecting an arbitrary server file path into the &amp;#39;convert.path&amp;#39; field of the &amp;#39;tiny_compress_images&amp;#39; post meta on an attachment they own, then triggering attachment deletion to invoke the vulnerable code path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The TinyPNG – JPEG, PNG &amp;amp; WebP image compression plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_converted_image_size function in all versions up to, and including, 3.6.13. This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). An attacker can exploit this by injecting an arbitrary server file path into the &amp;#39;convert.path&amp;#39; field of the &amp;#39;tiny_compress_images&amp;#39; post meta on an attachment they own, then triggering attachment deletion to invoke the vulnerable code path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-7311</guid>
    </item>
    <item>
      <title>GHSA-p2fp-6329-h7jp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p2fp-6329-h7jp</link>
      <description>&lt;p&gt;The TinyPNG – JPEG, PNG &amp;amp; WebP image compression plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_converted_image_size function in all versions up to, and including, 3.6.13. This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). An attacker can exploit this by injecting an arbitrary server file path into the &amp;#39;convert.path&amp;#39; field of the &amp;#39;tiny_compress_images&amp;#39; post meta on an attachment they own, then triggering attachment deletion to invoke the vulnerable code path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The TinyPNG – JPEG, PNG &amp;amp; WebP image compression plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_converted_image_size function in all versions up to, and including, 3.6.13. This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). An attacker can exploit this by injecting an arbitrary server file path into the &amp;#39;convert.path&amp;#39; field of the &amp;#39;tiny_compress_images&amp;#39; post meta on an attachment they own, then triggering attachment deletion to invoke the vulnerable code path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p2fp-6329-h7jp</guid>
    </item>
  </channel>
</rss>
