CVE-2026-16070

Brizy - Page Builder <= 2.8.18 - Insecure Direct Object Reference to Authenticated (Contributor+) Template Type Update

2026-07-27 00:00
Muni Nitish Kumar Yaddala

Strategic Overview

Status
Patched in 2.8.19
Affected Plugin
Brizy – Page Builder
Affected Version
<= 2.8.18
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-16070
View all Brizy – Page Builder vulnerabilities

At a glance

CVE-2026-16070 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Brizy WordPress plugin, affecting versions <= 2.8.18. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.8.19; sites on affected versions should update now. Disclosed July 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The Brizy - Page Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.8.18. This is due to a missing capability check and lack of integer casting on the template_id parameter in the setTemplateType() function, allowing any authenticated user to reference and modify any template post. This makes it possible for authenticated attackers, with contributor-level access and above, to update the template type of arbitrary templates, including those they do not own or have permission to edit.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Brizy <= 2.8.18 carries this weakness at setTemplateType(), and reaching it takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Brizy the fix is 2.8.19: builds <= 2.8.18 are affected, anything from 2.8.19 onward is not.

Remediation

Update to version 2.8.19, 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 2.8.19 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-16070https://www.wordfence.com/threat-intel/vulnerabilities/id/6cec3472-9778-44a6-b792-306288284b0ahttps://nvd.nist.gov/vuln/detail/CVE-2026-16070

Related records

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