CVE-2022-36425

Beaver Builder <= 2.5.4.3 - Missing Authorization

2022-07-20 00:00
Dave Jong

Strategic Overview

Status
Patched in 2.5.4.4
Affected Plugin
Beaver Builder Page Builder – Drag and Drop Website Builder
Affected Version
<= 2.5.4.3
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-36425
View all Beaver Builder Page Builder – Drag and Drop Website Builder vulnerabilities

At a glance

CVE-2022-36425 is a medium-severity Missing Authorization vulnerability in the Beaver Builder Page Builder WordPress plugin, affecting versions <= 2.5.4.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.5.4.4; sites on affected versions should update now. Disclosed July 2022, reported by Dave Jong.

Vulnerability Overview

The Beaver Builder plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the save_settings function in versions up to, and including, 2.5.4.3. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to disable the plugin.

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

CWE-862: Missing Authorization

Reaching this weakness in Beaver Builder Page Builder <= 2.5.4.3 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 Beaver Builder Page Builder the fix is 2.5.4.4: builds <= 2.5.4.3 are affected, anything from 2.5.4.4 onward is not.

Remediation

Update to version 2.5.4.4, 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: Beaver Builder Page Builder 2.5.4.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-36425https://www.wordfence.com/threat-intel/vulnerabilities/id/28f0a927-a92e-45ab-8ef3-7a7c9368e1e4https://nvd.nist.gov/vuln/detail/CVE-2022-36425

Related records

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