CVE-2026-1673

BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net <= 1.1.5 - Cross-Site Request Forgery to Taxonomy Term Deletion

2026-04-07 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 1.1.6
Affected Plugin
BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net
Affected Version
<= 1.1.5
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-1673
View all BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net vulnerabilities

At a glance

CVE-2026-1673 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the BEAR WordPress plugin, affecting versions <= 1.1.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.6; sites on affected versions should update now. Disclosed April 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

The BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.5. This is due to missing nonce validation on the woobe_delete_tax_term() function. This makes it possible for unauthenticated attackers to delete WooCommerce taxonomy terms (categories, tags, etc.) via a forged request granted they can trick a site administrator or shop manager into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

BEAR <= 1.1.5 carries this weakness at woobe_delete_tax_term(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For BEAR the fix is 1.1.6: builds <= 1.1.5 are affected, anything from 1.1.6 onward is not.

Remediation

Update to version 1.1.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to BEAR: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BEAR 1.1.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1673https://www.wordfence.com/threat-intel/vulnerabilities/id/1e4e8960-b0c1-4dbb-ba97-e45b88fb06c0https://nvd.nist.gov/vuln/detail/CVE-2026-1673

Related records

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