CVE-2026-1673 MEDIUM

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

Vendor Realmag777
Product BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net
Weakness CWE-352 · CSRF
Published April 8, 2026
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

BEAR – Bulk Editor and Products Manager Professional for WooCommerce versions up to 1.1.5 are vulnerable to cross-site request forgery (CSRF). An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions in the plugin without the admin's knowledge or consent. The vulnerability requires the admin to visit the attacker's page while authenticated to the WordPress site.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions in the plugin on behalf of a logged-in administrator without their knowledge.

Potential impact on your site

04Site Impact

An attacker could modify product data, settings, or perform bulk operations through the plugin if an admin visits a malicious link.

Conditions required to exploit

05Prerequisites

Administrator must be logged into WordPress and visit a page controlled by the attacker.

Key dates

06Disclosure timeline

April 8, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE