CVE-2026-16070

Brizy - Page Builder < 2.8.19 - Contributor+ Template Type Update via IDOR

Published Aug 4, 2026 CVSS 3.1 · 2.7 Low EPSS < 1% KEV · Not listed
Description
The Brizy WordPress plugin before 2.8.19 does not properly verify authorization on the object being modified before updating a template's type meta, validating a request parameter that is different from the one used in the write operation, allowing users with Contributor-level access and above to change the template-type assignment of templates owned by other users.

Analysis

AI-generated

Technical impact

CVE-2026-16070 exposes an authorization bypass in the Brizy WordPress plugin. The plugin fails to verify that the user modifying a template owns the template, instead comparing a request parameter unrelated to the write operation. Users with Contributor-level or higher privileges can therefore alter the template-type metadata of templates belonging to other users. This allows unauthorized manipulation of site layouts and could facilitate further privilege escalation.

Affected Systems

All WordPress installations running Brizy Page Builder before version 2.8.19 are affected. The flaw applies to sites that have users assigned the Contributor role or higher, regardless of the WordPress core version. No other plugins or components are mentioned. The impact is confined to the Brizy plugin’s template management interface.

Risk and Exploitability

The vulnerability has a CVSS score of 2.7 and an EPSS score of < 1%, indicating a relatively low exploitation probability. Based on the description, it is inferred that an attacker can modify template-type metadata as any authenticated user with Contributor or higher privileges. Because privilege escalation is straightforward once a contributor account exists, the risk for sites that expose this role widely is inferred to be high. No public exploit or KEV listing is documented, but the broad attack surface and simple exploitation path are inferred to warrant immediate attention. The potential for cascading effects is inferred, justifying a high priority for remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Brizy plugin update (v2.8.19 or newer) to close the authorization check.
  • If a patch is not yet available, revoke or downgrade the Contributor role on affected sites until the plugin is updated.
  • Deploy a web‑application firewall rule or input validation check that blocks requests attempting to change template types for templates not owned by the requester.

Generated by OpenCVE AI on August 4, 2026 at 21:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-284
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 2.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-284
CWE-639
Type Values Removed Values Added
First Time appeared Brizy
Brizy brizy
Wordpress
Wordpress wordpress
Vendors & Products Brizy
Brizy brizy
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Description The Brizy WordPress plugin before 2.8.19 does not properly verify authorization on the object being modified before updating a template's type meta, validating a request parameter that is different from the one used in the write operation, allowing users with Contributor-level access and above to change the template-type assignment of templates owned by other users.
Title Brizy - Page Builder < 2.8.19 - Contributor+ Template Type Update via IDOR
References
Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 4, 2026, 2:21 PM
Reserved
Jul 17, 2026, 1:18 PM
Status
Deferred
Published
Aug 4, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM