CVE-2026-1673
CSRF in BEAR WooCommerce Plugin Allows Taxonomy Deletion
Publication date: 2026-04-08
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pluginus | bulk_editor_and_products_manager_professional_for_woocommerce | to 1.1.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The BEAR β Bulk Editor and Products Manager Professional for WooCommerce plugin for WordPress has a Cross-Site Request Forgery (CSRF) vulnerability in all versions up to and including 1.1.5.
This vulnerability exists because the plugin's function woobe_delete_tax_term() lacks nonce validation, which is a security measure to verify that requests are legitimate.
As a result, an attacker can trick an authenticated site administrator or shop manager into performing an unwanted action, such as deleting WooCommerce taxonomy terms like categories or tags, by sending a forged request.
How can this vulnerability impact me? :
This vulnerability allows an unauthenticated attacker to cause an authenticated administrator or shop manager to delete WooCommerce taxonomy terms without their intention.
The impact includes potential disruption of the organization and categorization of products in the WooCommerce store, which can affect the store's operation and user experience.
Since the vulnerability does not affect confidentiality or availability, the impact is limited to integrity, specifically the unauthorized modification (deletion) of taxonomy terms.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the BEAR β Bulk Editor and Products Manager Professional for WooCommerce plugin to a version later than 1.1.5 where the nonce validation issue in the woobe_delete_tax_term() function is fixed.
Additionally, avoid clicking on suspicious links or performing actions from untrusted sources, especially if you have administrator or shop manager privileges on the affected WordPress site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a Cross-Site Request Forgery (CSRF) in the BEAR β Bulk Editor and Products Manager Professional for WooCommerce plugin, specifically due to missing nonce validation in the woobe_delete_tax_term() function.
To detect this vulnerability on your system, you can check if the plugin version is up to and including 1.1.5, as these versions are affected.
For network detection, monitoring for suspicious HTTP requests that attempt to invoke the woobe_delete_tax_term() function without proper authentication or nonce tokens could help identify exploitation attempts.
Since the vulnerability requires tricking an administrator or shop manager into clicking a malicious link, reviewing web server logs for unusual POST requests to endpoints related to taxonomy term deletion may be useful.
Specific commands to assist detection might include:
- Using grep on web server logs to find requests containing 'woobe_delete_tax_term' or related parameters, e.g., `grep -i woobe_delete_tax_term /var/log/apache2/access.log`
- Checking the installed plugin version via WP-CLI: `wp plugin get bulk-editor-and-products-manager-professional-for-woocommerce --field=version`
- Monitoring HTTP traffic for suspicious POST requests without valid nonce tokens targeting taxonomy term deletion URLs.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to delete WooCommerce taxonomy terms by tricking authorized users into performing actions via forged requests. This could potentially lead to unauthorized modification of data within the WooCommerce environment.
However, there is no direct information provided about how this vulnerability impacts compliance with common standards and regulations such as GDPR or HIPAA.