Bricksbuilder <= 1.9.6.1 - Authenticated (Contributor+) Privilege Escalation via create_autosave
Strategic Overview
- Status
- Patched in 1.9.7
- Affected Theme
- Bricks
- Affected Version
<= 1.9.6.1- CVSS
- 7.1High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2024-2297
At a glance
CVE-2024-2297 is a high-severity Improper Privilege Management vulnerability in the Bricks WordPress theme, affecting versions <= 1.9.6.1. It carries a CVSS score of 7.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.9.7; sites on affected versions should update now. Disclosed February 2025, reported by etragardh.
Vulnerability Overview
The Bricks theme for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.9.6.1. This is due to insufficient validation checks placed on the create_autosave AJAX function. This makes it possible for authenticated attackers, with contributor-level access and above, to execute arbitrary PHP code with elevated (administrator-level) privileges. NOTE: Successful exploitation requires (1) the Bricks Builder to be enabled for posts (2) Builder access to be enabled for contributor-level users, and (3) "Code Execution" to be enabled for administrator-level users within the theme's settings.
Technical Analysis
The vector marks this flaw as remotely reachable over the network. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
Reaching this weakness in Bricks <= 1.9.6.1 takes an account at Contributor level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Bricks the fix is 1.9.7: builds <= 1.9.6.1 are affected, anything from 1.9.7 onward is not.
Remediation
Update to version 1.9.7, 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 1.9.7 closes this, and updating the theme is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Bricks
- 9.8CVE-2024-25600: Bricks <= 1.9.6 Remote Code Execution
CVE-2024-25600 - 8.8CVE-2022-3401: Bricks 1.2 - 1.5.3 Remote Code Execution
CVE-2022-3401 - 7.5CVE-2025-6495: Bricks Builder <= 1.12.4 SQL Injection
CVE-2025-6495 - 6.5CVE-2022-3400: Bricks 1.0… Arbitrary Content Creation/Modification
CVE-2022-3400 - 6.1CVE-2026-41554: Bricks <= 1.9.2 Reflected Cross-Site Scripting
CVE-2026-41554 - 5.4CVE-2023-3410: Bricks <= 1.10.1 Stored Cross-Site Scripting
CVE-2023-3410 - 5.4CVE-2023-3409: Bricks <= 1.8.1 Cross-Site Request Forgery
CVE-2023-3409 - 4.3CVE-2023-3408: Bricks <= 1.8.1 Cross-Site Request Forgery
CVE-2023-3408
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C