dbcve.org
BrizyWordPress extension

CVE-2024-1296

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 2.4.41 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's block upload in all versions up to, and including, 2.4.40 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 contains a stored XSS vulnerability in versions up to 2.4.40. Attackers with contributor-level or higher permissions can inject malicious scripts through the plugin's block upload feature due to insufficient input sanitization and output escaping on user-supplied attributes. These scripts execute whenever users access injected pages.

MitigationUpdate the Brizy Page Builder plugin to version 2.4.41 or later to patch the sanitization and escaping vulnerabilities. Review and monitor contributed content for existing malicious injections.

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
BrizyWordPress extension
Affected:< 2.4.41

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installed Brizy plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Brizy Page Builder. The version number is displayed under the plugin name. Alternatively, check the plugin header in /wp-content/plugins/brizy/ folder or query the WordPress database for the plugin version option.
    Affected if The installed version is lower than 2.4.41 (e.g., 2.4.40, 2.4.39, etc.)
  2. Verify contributor or higher permission users exist
    Navigate to Users > All Users in WordPress admin. Review the Role column for any accounts assigned Contributor, Author, Editor, or Administrator roles. These roles have the capability to access the block upload feature.
    Affected if At least one user account has contributor-level or higher permissions and can access the Brizy editor.
  3. Confirm block upload feature is accessible
    Log in as a user with contributor permissions or higher. Create or edit a post/page using the Brizy editor. Look for the block upload or import functionality within the Brizy interface. The vulnerability exists in the block upload feature specifically.
    Affected if The block upload feature is available and functional for users with contributor permissions or higher.
  4. Inspect existing Brizy content for suspicious scripts
    Search the WordPress database for post content containing the brizy editor or examine posts/pages created with Brizy. Look for unexpected script tags, javascript: URIs, or event handler attributes (onload, onerror, onmouseover) within the postmeta table where Brizy stores content. Use SQL: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%onerror=%' (adjust prefix if non-standard).
    Affected if Malicious script injections are found in Brizy-stored post content or meta records.

The environment is affected if Brizy plugin version is below 2.4.41 AND users with contributor-level or higher permissions have access to the block upload feature, or if malicious injections already exist in Brizy content.

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 2.4.41 or later
Fixed in 2.4.41
Interim mitigation

Update the Brizy Page Builder plugin to version 2.4.41 or later to patch the sanitization and escaping vulnerabilities. Review and monitor contributed content for existing malicious injections.

Recommended fix High confidence

Brizy Page Builder 2.4.41

  1. Backup your WordPress site database and files
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find the Brizy – Page Builder plugin and click 'Update now' to upgrade to version 2.4.41 or later
  4. Verify the plugin version after update confirms 2.4.41 or higher is installed

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

Fix this in Brizy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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