CVE-2025-4370

Brizy <= 2.6.20 - Missing Authorization to Unauthenticated Limited File Upload

2025-07-28 16:22
mikemyers

Strategic Overview

Status
Patched in 2.6.21
Affected Plugin
Brizy – Page Builder
Affected Version
<= 2.6.20
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-4370
View all Brizy – Page Builder vulnerabilities

At a glance

CVE-2025-4370 is a medium-severity Missing Authorization vulnerability in the Brizy WordPress plugin, affecting versions <= 2.6.20. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.6.21; sites on affected versions should update now. Disclosed July 2025, reported by mikemyers.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Brizy <= 2.6.20 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Brizy the fix is 2.6.21: builds <= 2.6.20 are affected, anything from 2.6.21 onward is not.

Remediation

Update to version 2.6.21, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Brizy 2.6.21 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C