CVE-2024-3711

Brizy – Page Builder <= 2.4.43 - Missing Authorization

2024-05-22 17:00
Lucio Sá

Strategic Overview

Status
Patched in 2.4.44
Affected Plugin
Brizy – Page Builder
Affected Version
<= 2.4.43
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-3711
View all Brizy – Page Builder vulnerabilities

At a glance

CVE-2024-3711 is a medium-severity Missing Authorization vulnerability in the Brizy WordPress plugin, affecting versions <= 2.4.43. It carries a CVSS score of 4.3 (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.4.44; sites on affected versions should update now. Disclosed May 2024, reported by Lucio Sá.

Vulnerability Overview

The Brizy – Page Builder plugin for WordPress is vulnerable to unauthorized plugin setting update due to a missing capability check on the functions action_request_disable, action_change_template, and action_request_enable in all versions up to, and including, 2.4.43. This makes it possible for authenticated attackers, with contributor access or above, to enable/disable the Brizy editor and modify the template used.

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 Brizy <= 2.4.43 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 Brizy the fix is 2.4.44: builds <= 2.4.43 are affected, anything from 2.4.44 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-3711https://www.wordfence.com/threat-intel/vulnerabilities/id/7092ce4a-bad9-4426-b94e-d9d688344272https://nvd.nist.gov/vuln/detail/CVE-2024-3711

Related records

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