dbcve.org
BricksWordPress extension · Bricksbuilder

CVE-2022-3401

HIGH · 8.8 CVSS v3.1 Published 2022-10-28
Fix available
A fix is available. Upgrade to 1.5.4 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 remote code execution due to the theme allowing site editors to include executable code blocks in website content in versions 1.2 to 1.5.3. This, combined with the missing authorization vulnerability (CVE-2022-3400), makes it possible for authenticated attackers with minimal permissions, such as a subscriber, can edit any page, post, or template on the vulnerable WordPress website and inject a code execution block that can be used to achieve remote code execution.

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 (versions 1.2-1.5.3) allows executable code blocks in content editor fields, and when combined with CVE-2022-3400's authorization bypass, any authenticated user with subscriber-level permissions can inject and execute arbitrary PHP code on the server by editing pages, posts, or templates.

MitigationUpdate Bricks theme to version 1.5.4 or later which patches this vulnerability; alternatively, disable user registration or restrict the subscriber role until the update can be applied.

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.2, < 1.5.4

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. Confirm Bricks theme is installed
    Navigate to Appearance > Themes in WordPress admin dashboard and verify if the Bricks theme appears in the theme list. Alternatively, check the wp-content/themes directory for a bricks folder.
    Affected if Bricks theme is installed and active
  2. Identify installed Bricks version
    Check the style.css file in wp-content/themes/bricks/ for the 'Version:' header, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'template' OR option_name = 'stylesheet'; then check the version via file inspection.
    Affected if Version is greater than or equal to 1.2 and less than 1.5.4
  3. Verify user registration is enabled
    In WordPress admin, go to Settings > General and check 'Anyone can register' is enabled. Or query: SELECT option_value FROM wp_options WHERE option_name = 'users_can_register';
    Affected if User registration is enabled (users_can_register = 1)
  4. Check for subscriber-level users
    In WordPress admin, go to Users > All Users and review the role column. Or query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%subscriber%';
    Affected if At least one user exists with subscriber role

A user is affected if Bricks theme versions 1.2 through 1.5.3 are installed, user registration is enabled, and any subscriber-level user account exists in the WordPress environment.

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.5.4 or later
Fixed in 1.5.4
Interim mitigation

Update Bricks theme to version 1.5.4 or later which patches this vulnerability; alternatively, disable user registration or restrict the subscriber role until the update can be applied.

Recommended fix High confidence

Bricks theme version 1.5.4 or later

  1. 1. Create a complete backup of the WordPress site (database and files)
  2. 2. Navigate to Dashboard > Appearance > Themes in WordPress admin
  3. 3. Locate the Bricks theme and click on 'Update Now' to upgrade to version 1.5.4 or later
  4. 4. Alternatively, download the latest Bricks theme from the official bricksbuilder.io website and upload it via WordPress theme uploader
  5. 5. After updating, verify the version number reflects 1.5.4 or higher
  6. 6. Audit WordPress user accounts for unauthorized subscribers or administrators added during the compromise
  7. 7. Review posts, pages, and templates for any suspicious code execution blocks that may have been injected
  8. 8. Consider resetting passwords for all user accounts as a precaution
Caveat Standard theme update - review any custom styling or builder settings after upgrade as minor visual changes may occur

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

Fix this in Bricks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3401 — 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-2022-3401 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