<?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://vulnerability.circl.lu</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, 28 Sep 2026 11:14:19 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-15095</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-15095</link>
      <description>&lt;p&gt;The Product Feed Manager for WooCommerce – CTX Feed – Support 220+ Shopping &amp;amp; Social Channels plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 6.6.43 via the &amp;#39;provider&amp;#39; parameter. This makes it possible for authenticated attackers, with shop manager-level access and above, to delete arbitrary files on the server, which can lead to remote code execution when critical files are deleted. Exploitation requires two sequential REST API calls: first to /wp-json/ctxfeed/v1/make_feed/save_feed_config to persist the traversal payload in wp_options, then to /wp-json/ctxfeed/v1/manage_feeds/delete_feed to trigger the unlink(); deletion is further constrained to files whose extensions match the plugin&amp;#39;s validated whitelist (csv, xml, tsv, xls, xlsx, json, txt).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Product Feed Manager for WooCommerce – CTX Feed – Support 220+ Shopping &amp;amp; Social Channels plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 6.6.43 via the &amp;#39;provider&amp;#39; parameter. This makes it possible for authenticated attackers, with shop manager-level access and above, to delete arbitrary files on the server, which can lead to remote code execution when critical files are deleted. Exploitation requires two sequential REST API calls: first to /wp-json/ctxfeed/v1/make_feed/save_feed_config to persist the traversal payload in wp_options, then to /wp-json/ctxfeed/v1/manage_feeds/delete_feed to trigger the unlink(); deletion is further constrained to files whose extensions match the plugin&amp;#39;s validated whitelist (csv, xml, tsv, xls, xlsx, json, txt).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-15095</guid>
    </item>
    <item>
      <title>GHSA-mmq2-8hq5-2c6q</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-mmq2-8hq5-2c6q</link>
      <description>&lt;p&gt;The Product Feed Manager for WooCommerce – CTX Feed – Support 220+ Shopping &amp;amp; Social Channels plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 6.6.43 via the &amp;#39;provider&amp;#39; parameter. This makes it possible for authenticated attackers, with shop manager-level access and above, to delete arbitrary files on the server, which can lead to remote code execution when critical files are deleted. Exploitation requires two sequential REST API calls: first to /wp-json/ctxfeed/v1/make_feed/save_feed_config to persist the traversal payload in wp_options, then to /wp-json/ctxfeed/v1/manage_feeds/delete_feed to trigger the unlink(); deletion is further constrained to files whose extensions match the plugin&amp;#39;s validated whitelist (csv, xml, tsv, xls, xlsx, json, txt).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Product Feed Manager for WooCommerce – CTX Feed – Support 220+ Shopping &amp;amp; Social Channels plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 6.6.43 via the &amp;#39;provider&amp;#39; parameter. This makes it possible for authenticated attackers, with shop manager-level access and above, to delete arbitrary files on the server, which can lead to remote code execution when critical files are deleted. Exploitation requires two sequential REST API calls: first to /wp-json/ctxfeed/v1/make_feed/save_feed_config to persist the traversal payload in wp_options, then to /wp-json/ctxfeed/v1/manage_feeds/delete_feed to trigger the unlink(); deletion is further constrained to files whose extensions match the plugin&amp;#39;s validated whitelist (csv, xml, tsv, xls, xlsx, json, txt).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-mmq2-8hq5-2c6q</guid>
    </item>
  </channel>
</rss>
