CVE-2024-24835

BEAR <= 1.1.4 - Missing Authorization via Several Functions

2024-02-02 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Patched in 1.1.4.1
Affected Version
<= 1.1.4
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-24835
View all BEAR – Bulk Editor for WooCommerce Professional. AI assistant on board (MCP Server) vulnerabilities

At a glance

CVE-2024-24835 is a medium-severity Missing Authorization vulnerability in the BEAR WordPress plugin, affecting versions <= 1.1.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.4.1; sites on affected versions should update now. Disclosed February 2024, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

The BEAR plugin for WordPress is vulnerable to unauthorized access due to missing capability checks on several functions in the /ext/history/history.php file in versions up to, and including, 1.1.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform several unauthorized actions.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in BEAR <= 1.1.4 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For BEAR the fix is 1.1.4.1: builds <= 1.1.4 are affected, anything from 1.1.4.1 onward is not.

Remediation

Update to version 1.1.4.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: BEAR 1.1.4.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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