dbcve.org
BricksWordPress extension · Bricksbuilder

CVE-2024-2297

HIGH · 8.8 CVSS v3.1 Published 2025-02-27
Fix available
A fix is available. Upgrade to 1.9.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Bricks WordPress theme lacks proper authorization validation in its create_autosave AJAX function, allowing authenticated users with contributor-level permissions to trigger administrator-privileged PHP code execution when specific theme settings are enabled (Builder for posts, contributor builder access, and admin-level code execution settings).

MitigationUpdate Bricks theme to version 1.9.7 or later and review/disable the 'Code Execution' setting unless strictly necessary, while ensuring contributor-level users do not have Builder access unless required for site functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BricksWordPress extension
Affected:< 1.9.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Bricks theme is installed
    Check your WordPress installation themes directory or view the theme information in WP Admin under Appearance > Themes. Look for 'Bricksbuilder' or 'Bricks' theme.
    Affected if Bricks theme is active on the WordPress site
  2. Determine the installed Bricks version
    In WordPress Admin, go to Bricks > Settings > General (or check theme files for version number in style.css or similar). Compare the version number to the affected range: versions prior to 1.9.7 are vulnerable.
    Affected if The installed Bricks version is lower than 1.9.7
  3. Verify if Builder for posts is enabled
    In WordPress Admin, navigate to Bricks > Settings > Builder > Post Types. Check if 'Posts' or other post types have the Builder option enabled.
    Affected if Builder for posts is enabled (the specific post type being used is checked)
  4. Verify if contributor builder access is enabled
    In WordPress Admin, go to Bricks > Settings > User Roles or Builder Access. Check if contributors have been granted builder/editor access.
    Affected if Contributor-level users have builder access enabled
  5. Verify if code execution settings are enabled
    In WordPress Admin, go to Bricks > Settings > Builder > Code Execution (or similar section under Builder settings). Check if PHP code execution or dynamic data settings that allow PHP are enabled.
    Affected if Code execution settings are enabled in the Builder configuration

A site is affected if it runs Bricks theme version below 1.9.7 AND has Builder for posts enabled AND contributor builder access enabled AND code execution settings enabled - all conditions must be present for exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.7 or later
Fixed in 1.9.7
Interim mitigation

Update Bricks theme to version 1.9.7 or later and review/disable the 'Code Execution' setting unless strictly necessary, while ensuring contributor-level users do not have Builder access unless required for site functionality.

Recommended fix High confidence

1.9.7

  1. Backup the WordPress database and files before proceeding
  2. Navigate to Dashboard > Appearance > Themes in WordPress admin
  3. Deactivate the current Bricks theme
  4. Delete the existing Bricks theme installation
  5. Upload and install Bricks version 1.9.7 or later
  6. Activate the new Bricks theme version
  7. Verify the theme version shows 1.9.7 or higher in Appearance > Themes
Caveat Review theme settings and customizations after upgrade as with any theme update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bricks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2297 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data