Bricks Builder <= 1.9.8 - Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 1.9.9
- Affected Plugin
- Bricks Builder
- Affected Version
<= 1.9.8- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-4874
At a glance
CVE-2024-4874 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Bricks Builder WordPress plugin, affecting versions <= 1.9.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 1.9.9; sites on affected versions should update now. Disclosed June 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Bricks Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.9.8 via the postId parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to modify posts and pages created by other users including admins. As a requirement for this, an admin would have to enable access to the editor specifically for such a user or enable it for all users with a certain user account type.
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Bricks Builder <= 1.9.8 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Bricks Builder the fix is 1.9.9: builds <= 1.9.8 are affected, anything from 1.9.9 onward is not.
Remediation
Update to version 1.9.9, 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: Bricks Builder 1.9.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C