Brizy - Page Builder < 1.0.114 - Missing Authorization to Settings Update

2020-03-05 00:00

Strategic Overview

Status: Patched in 1.0.114
Affected Plugin: Brizy – Page Builder
Affected Version: < 1.0.114
CVSS: 6.5Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE pending

View all Brizy – Page Builder vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Brizy WordPress plugin, affecting versions < 1.0.114. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.114; sites on affected versions should update now. Disclosed March 2020, reported by riki aji.

Vulnerability Overview

The Brizy - Page Builder plugin for WordPress is vulnerable to authorization bypass due to a missing capability check and direct file access to /brizy/admin/site-settings.php in versions up to 1.0.114. This makes it possible for unauthenticated attackers to access the settings page and make modifications to the site's settings. This could be used to inject XSS.

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 < 1.0.114 takes a caller who can reach the endpoint. 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 1.0.114: builds < 1.0.114 are affected, anything from 1.0.114 onward is not.

Remediation

Update to version 1.0.114, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Brizy 1.0.114 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/ba98a282-39ee-4a84-b988-ecfc0c4cd297

Related records

Same weakness class

Other vulnerabilities in Brizy – Page Builder

CVSS Vector

6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityLow

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/