dbcve.org
BrizyWordPress extension

CVE-2025-4370

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-29
Fix available
A fix is available. Upgrade to 2.6.21 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 for WordPress is vulnerable to limited file uploads due to missing authorization on process_external_asset_urls function as well as missing path validation in store_file function in all versions up to, and including, 2.6.20. This makes it possible for unauthenticated attackers to upload .TXT files on the affected site's server.

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 an authenticated file upload vulnerability in versions up to 2.6.20. The issue stems from missing authorization checks on the process_external_asset_urls function and insufficient path validation in the store_file function, allowing unauthenticated attackers to upload .TXT files to the server.

MitigationUpdate to the latest version of the Brizy plugin (2.6.21 or higher) which includes proper authorization checks and path validation. Until patched, consider restricting access to the affected endpoints via web server configuration.

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.6.21

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Brizy plugin installation
    Check if the Brizy Page Builder plugin is installed on the WordPress site. Navigate to WordPress Admin > Plugins or inspect the /wp-content/plugins/ directory for a brizy folder.
    Affected if The brizy folder exists in the plugins directory and the plugin is active.
  2. Verify installed version
    Check the plugin version number. In WordPress Admin, go to Plugins > Brizy > View Details, or read the 'Version' header from the main plugin file at /wp-content/plugins/brizy/brizy.php.
    Affected if The reported version is lower than 2.6.21 (for example: 2.6.20, 2.6.19, etc.).
  3. Confirm vulnerable functions exist
    Inspect the Brizy plugin source code for the process_external_asset_urls and store_file functions. Search in /wp-content/plugins/brizy/ for these function definitions.
    Affected if Both functions exist in the plugin code, indicating the vulnerable code path is present.
  4. Check endpoint accessibility
    Test whether the affected AJAX/action endpoints used by these functions are accessible. These are typically found in the plugin's admin-ajax.php hooks or direct AJAX handlers.
    Affected if The endpoints respond and accept requests, suggesting the attack surface is exposed.

If the Brizy plugin is installed, active, and running a version lower than 2.6.21, the environment is affected by this file upload vulnerability.

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.6.21 or later
Fixed in 2.6.21
Interim mitigation

Update to the latest version of the Brizy plugin (2.6.21 or higher) which includes proper authorization checks and path validation. Until patched, consider restricting access to the affected endpoints via web server configuration.

Recommended fix High confidence

2.6.21

  1. Backup your WordPress site before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the Brizy – Page Builder plugin
  5. Click 'Update Now' to update to the latest version
  6. Verify the updated version is 2.6.21 or higher after the update completes

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

Fix this in Brizy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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