External risk intelligence

WPFactory Product Filter Blind SQL Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-112866

The vulnerability exists in a WordPress plugin designed for product filtering on e-commerce websites. Such plugins are typically integrated into the public-facing front end of websites, making the vulnerable functionality accessible to internet users browsing the site.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A SQL Injection vulnerability has been identified in the Product Filter by WBW plugin, which is used on websites for managing product filtering. This issue could allow attackers to interfere with database commands.

  • Attackers can inject harmful database commands.
  • It impacts e-commerce product filtering features.
  • Confirm relevance and determine if exposure exists.

Attack Path

How an attacker could exploit the issue

An attacker could target websites using a specific product filter plugin. By sending specially crafted data through the plugin's filtering features, an attacker might trick the application into executing unintended SQL commands. This could potentially lead to unauthorized access to sensitive data.

  • No special access needed.
  • Filtering feature accepts malicious input.
  • Potential for sensitive data exposure.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to inject malicious SQL commands into the product filter, potentially leading to the exposure of sensitive data from the website's database. This could occur when a user interacts with the product filtering feature, and the filter's backend improperly processes specially crafted input.

  • Database content exposure.
  • Via crafted product filter input.
  • May reveal sensitive site data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This SQL injection vulnerability in a WordPress e-commerce plugin necessitates immediate attention from teams managing public-facing websites. The first step is to identify all instances of the affected plugin, determine their reachability from the internet, assess their business criticality, and locate the accountable owner for remediation planning.

  • Application and infrastructure owners.
  • Verify plugin exposure and criticality.
  • Plan remediation or mitigation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Product Filter by WBW?

It is a WordPress plugin designed for e-commerce sites to help shoppers sort and narrow down product lists. By integrating directly into a store's front-end, it provides the interactive interface that allows users to filter items by categories, attributes, or price, effectively acting as an extension of the website's database query capabilities.

How does CVE-2026-112866 work?

This vulnerability is classified as Improper Neutralization of Special Elements used in an SQL Command, or SQL Injection (CWE-89). It occurs when the plugin fails to properly sanitize user input before passing it to the database. An attacker can leverage this flaw to send malicious SQL queries, allowing them to manipulate the database or potentially extract sensitive information that they are not authorized to view.

When does this vulnerability trigger?

The flaw is triggered when the plugin processes specially crafted input through its filtering features. It is important to note that the issue resides in the plugin's data processing logic; simply viewing a page with a filter does not trigger the bug. Instead, the malicious command must be explicitly provided through the input fields that the plugin uses to construct its database queries.

Do I need to worry about this if my site is internal?

According to Halo Surface Signal, this vulnerability is particularly concerning for public-facing websites. Because the plugin is designed to be part of an e-commerce store's public interface, the vulnerable functionality is typically reachable by anyone browsing the internet. If your installation is strictly internal and not accessible to the public, the risk profile changes significantly.

How should I respond to this threat?

Start by identifying every website running the affected plugin versions. Determine if these sites are internet-facing and assess the sensitivity of the data stored in their databases. Once you have a clear inventory, work with the accountable application owners to plan for updates or implement temporary mitigations to restrict access to the affected filtering functionality.

References