<?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>Sun, 18 Oct 2026 07:42:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-3138 — Product Filter for WooCommerce by WBW &lt;= 3.1.2 - Missing Authorization to Unauthenticated Filter Data Deletion via TRUN…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-3138</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; woobewoo Product Filter for WooCommerce by WBW&lt;/p&gt;
&lt;p&gt;The Product Filter for WooCommerce by WBW plugin for WordPress is vulnerable to unauthorized data loss due to a missing capability check in all versions up to, and including, 3.1.2. This is due to the plugin&amp;#39;s MVC framework dynamically registering unauthenticated AJAX handlers via `wp_ajax_nopriv_` hooks without verifying user capabilities, combined with the base controller&amp;#39;s `__call()` magic method forwarding undefined method calls to the model layer, and the `havePermissions()` method defaulting to `true` when no permissions are explicitly defined. This makes it possible for unauthenticated attackers to truncate the plugin&amp;#39;s `wp_wpf_filters` database table via a crafted AJAX request with `action=delete`, permanently destroying all filter configurations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; woobewoo Product Filter for WooCommerce by WBW&lt;/p&gt;
&lt;p&gt;The Product Filter for WooCommerce by WBW plugin for WordPress is vulnerable to unauthorized data loss due to a missing capability check in all versions up to, and including, 3.1.2. This is due to the plugin&amp;#39;s MVC framework dynamically registering unauthenticated AJAX handlers via `wp_ajax_nopriv_` hooks without verifying user capabilities, combined with the base controller&amp;#39;s `__call()` magic method forwarding undefined method calls to the model layer, and the `havePermissions()` method defaulting to `true` when no permissions are explicitly defined. This makes it possible for unauthenticated attackers to truncate the plugin&amp;#39;s `wp_wpf_filters` database table via a crafted AJAX request with `action=delete`, permanently destroying all filter configurations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-3138</guid>
    </item>
  </channel>
</rss>
