dbcve.org
Brizy Page BuilderApplication · Brizy

CVE-2021-38345

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-14
Fix available
A fix is available. Upgrade to 1.0.1.126 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Brizy Page Builder plugin <= 2.3.11 for WordPress used an incorrect authorization check that allowed any logged-in user accessing any endpoint in the wp-admin directory to modify the content of any existing post or page created with the Brizy editor. An identical issue was found by another researcher in Brizy <= 1.0.125 and fixed in version 1.0.126, but the vulnerability was reintroduced in version 1.0.127.

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 Brizy Page Builder plugin for WordPress had a broken access control vulnerability where incorrect authorization checks allowed any authenticated user (regardless of role/permissions) to modify content of any existing post or page created with the Brizy editor by accessing endpoints in the wp-admin directory.

MitigationUpdate Brizy Page Builder to version 2.3.12 or later (or version 1.0.126+ for the 1.x branch) to patch the re-introduced authorization bypass vulnerability.

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
Brizy Page BuilderApplication
Affected:< 1.0.1.126>= 1.0.127, <= 2.3.11

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
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 checks

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

  1. Identify if Brizy Page Builder is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Brizy Page Builder' in the list, or check the filesystem at /wp-content/plugins/
    Affected if The plugin is present in the installation
  2. Determine installed Brizy version
    In WordPress admin_plugins page, find Brizy Page Builder and note the version number displayed, or read the version from the plugin main file header at /wp-content/plugins/brizy/brizy.php
    Affected if The version is less than 1.0.126, or is between 1.0.127 and 2.3.11 inclusive
  3. Identify if Brizy-created content exists
    Query the WordPress database for posts with 'brizy' in post_type or check wp_postmeta for '_brizy_post_uid' meta_key, or look for posts using the Brizy editor in the Pages/Posts list
    Affected if There are posts or pages created using the Brizy editor (these are the targets of the vulnerability)
  4. Verify user role configuration
    Review user roles in WordPress admin under Users > All Users to confirm lower-privileged users (such as Subscribers or Contributors) exist on the site
    Affected if Any authenticated user with limited privileges can access wp-admin and thus the vulnerable endpoints if Brizy is vulnerable

You are affected if Brizy Page Builder is installed with a version less than 1.0.126 or between 1.0.127 and 2.3.11, AND there are existing posts or pages created with the Brizy editor on your site.

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.0.1.126 or later
Fixed in 1.0.1.126
Interim mitigation

Update Brizy Page Builder to version 2.3.12 or later (or version 1.0.126+ for the 1.x branch) to patch the re-introduced authorization bypass vulnerability.

Recommended fix Moderate confidence

Brizy Page Builder >= 2.3.12 or latest 2.x release; for 1.x branch use 1.0.126 if available

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Brizy Page Builder plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, you can manually download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify that the version is >= 2.3.12 (for the 2.x branch) or >= 1.0.126 but not reintroduced version (for 1.x branch)

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

Fix this in Brizy Page Builder Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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