CVE-2024-1937

Brizy – Page Builder <= 2.4.44 - Missing Authorization to Authenticated (Contributor+) Post Modification

2024-07-15 00:00
stealthcopter

Strategic Overview

Status
Patched in 2.4.45
Affected Plugin
Brizy – Page Builder
Affected Version
<= 2.4.44
CVSS
7.1High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1937
View all Brizy – Page Builder vulnerabilities

At a glance

CVE-2024-1937 is a high-severity Missing Authorization vulnerability in the Brizy WordPress plugin, affecting versions <= 2.4.44. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.4.45; sites on affected versions should update now. Disclosed July 2024, reported by stealthcopter.

Vulnerability Overview

The Brizy – Page Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_item' function in all versions up to, and including, 2.4.44. This makes it possible for authenticated attackers, with contributor access and above, to modify the content of arbitrary published posts, which includes the ability to insert malicious JavaScript.

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. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Brizy <= 2.4.44 carries this weakness at update_item, and reaching it takes an account at Contributor level or above. 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.45: builds <= 2.4.44 are affected, anything from 2.4.45 onward is not.

Remediation

Update to version 2.4.45, 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.45 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-1937https://www.wordfence.com/threat-intel/vulnerabilities/id/bb5f73c3-f40b-45d5-9947-c1a514d230f7https://nvd.nist.gov/vuln/detail/CVE-2024-1937

Related records

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