CVE-2025-11269

Product Filter by WBW <= 3.0.0 - Missing Authorization to Unauthenticated Settings Update

2025-10-24 17:28
Lucas Montes (NiRoX)

Strategic Overview

Status
Patched in 3.0.1
Affected Version
<= 3.0.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-11269
View all Product Filter for WooCommerce by WBW vulnerabilities

At a glance

CVE-2025-11269 is a medium-severity Missing Authorization vulnerability in the Product Filter for WooCommerce by WBW WordPress plugin, affecting versions <= 3.0.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.1; sites on affected versions should update now. Disclosed October 2025, reported by Lucas Montes (NiRoX).

Vulnerability Overview

The Product Filter by WBW plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'approveNotice' action in all versions up to, and including, 3.0.0. This makes it possible for unauthenticated attackers to update the plugin's settings.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Product Filter for WooCommerce by WBW <= 3.0.0 carries this weakness at approveNotice, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Product Filter for WooCommerce by WBW the fix is 3.0.1: builds <= 3.0.0 are affected, anything from 3.0.1 onward is not.

Remediation

Update to version 3.0.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Product Filter for WooCommerce by WBW 3.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C