CVE-2023-4926

BEAR <= 1.1.3.3 - Cross-Site Request Forgery to Product Deletion

2023-09-25 00:00
Marco Wotschka

Strategic Overview

Status
Patched in 1.1.4
Affected Plugin
BEAR – Bulk Editor for WooCommerce Professional. AI assistant on board (MCP Server)
Affected Version
<= 1.1.3.3
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-4926
View all BEAR – Bulk Editor for WooCommerce Professional. AI assistant on board (MCP Server) vulnerabilities

At a glance

CVE-2023-4926 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the BEAR WordPress plugin, affecting versions <= 1.1.3.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.4; sites on affected versions should update now. Disclosed September 2023, reported by Marco Wotschka.

Vulnerability Overview

The BEAR for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.3.3. This is due to missing or incorrect nonce validation on the woobe_bulk_delete_products function. This makes it possible for unauthenticated attackers to delete products via a forged request granted they can trick a site administrator 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)

Reaching this weakness in BEAR <= 1.1.3.3 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.4: builds <= 1.1.3.3 are affected, anything from 1.1.4 onward is not.

Remediation

Update to version 1.1.4, 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.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-4926https://www.wordfence.com/threat-intel/vulnerabilities/id/ab633506-63a1-4be1-b402-c7f0bcc4ea7ahttps://nvd.nist.gov/vuln/detail/CVE-2023-4926

Related records

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