BricksWordPress extension · Bricksbuilder
CVE-2022-3400
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 · uneditedThe Bricks theme for WordPress is vulnerable to authorization bypass due to a missing capability check on the bricks_save_post AJAX action in versions 1.0 to 1.5.3. This makes it possible for authenticated attackers with minimal permissions, such as a subscriber, to edit any page, post, or template on the vulnerable WordPress website.
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 confidenceThe Bricks WordPress theme (versions 1.0-1.5.3) lacks a capability check on the bricks_save_post AJAX action, allowing any authenticated user with subscriber-level permissions to edit any post, page, or template on the WordPress site. This is a broken access control vulnerability enabling privilege escalation.
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
>= 1.0, <= 1.5.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Bricks theme versionCheck the installed Bricks theme version in WordPress via Appearance > Themes or by inspecting the style.css file in the bricks theme directoryAffected if The installed version is 1.0, 1.5, 1.5.1, 1.5.2, or 1.5.3 (any version from 1.0 through 1.5.3 inclusive)
-
Confirm WordPress user registration statusNavigate to WordPress Settings > General and check if the 'Membership' option 'Anyone can register' is enabledAffected if User registration is enabled, allowing any new user to register with subscriber-level access and exploit this vulnerability
-
Verify AJAX action accessibilityInspect the bricks_save_post AJAX action handler in the theme files (typically in includes/ajax.php or similar) to confirm no capability check exists before the vulnerable codeAffected if The AJAX handler lacks a current_user_can() or similar capability verification check before processing the save request
-
Check for active subscriber accountsReview WordPress Users > All Users to identify any accounts with the Subscriber roleAffected if There are subscriber-level users present in the system who could leverage this flaw to modify content
You are affected if the Bricks theme version is 1.0 through 1.5.3 inclusive, user registration is enabled, and subscriber-level accounts exist or could be created.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Bricks theme to version 1.5.4 or later which includes the capability check fix. Alternatively, disable user registration if not needed or restrict AJAX access via server-side configuration.
Bricks theme version 1.5.4 or later
- 1. Log in to the WordPress admin dashboard with administrator privileges
- 2. Navigate to Appearance > Themes
- 3. Locate the Bricks theme
- 4. Check for available theme updates or upgrade to the latest version of Bricks theme
- 5. If automatic updates are not enabled, manually download the latest version from bricksbuilder.io
- 6. Upload and activate the updated Bricks theme
- 7. Verify the theme version in the WordPress admin to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Bricks
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3400 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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