<?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://db.gcve.eu</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, 12 Oct 2026 23:08:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-104801 — PPOM &lt;= 34.0.10 - Unauthenticated Arbitrary File Deletion via 'ppom[fields][&lt;data_name&gt;][n][org]' Parameter</title>
      <link>https://db.gcve.eu/vuln/cve-2026-104801</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; themeisle PPOM – Product Addons &amp;amp; Custom Fields for WooCommerce&lt;/p&gt;
&lt;p&gt;The PPOM – Product Addons &amp;amp; Custom Fields for WooCommerce plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the rename_files function in all versions up to, and including, 34.0.10 This makes it possible for unauthenticated attackers 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). The relocated file is moved byte-identically into the publicly accessible wp-content/uploads/ppom_files/confirmed/ directory, meaning the attack also results in arbitrary file read for any web-readable file on the server.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; themeisle PPOM – Product Addons &amp;amp; Custom Fields for WooCommerce&lt;/p&gt;
&lt;p&gt;The PPOM – Product Addons &amp;amp; Custom Fields for WooCommerce plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the rename_files function in all versions up to, and including, 34.0.10 This makes it possible for unauthenticated attackers 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). The relocated file is moved byte-identically into the publicly accessible wp-content/uploads/ppom_files/confirmed/ directory, meaning the attack also results in arbitrary file read for any web-readable file on the server.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-104801</guid>
    </item>
  </channel>
</rss>
