WordPress plugin · Updated daily · Source: Wordfence Intelligence

Brizy vulnerabilities: affected versions and fixes

Brizy has 60,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Brizy at a glance

  • 37 publicly disclosed vulnerabilities, 11 of them rated High or Critical. The most recent was disclosed on Nov 13, 2026.
  • Ranked #627 by popularity on WordPress.org (60,000+ active installs).
  • The latest version is 2.8.26 (released Nov 11, 2026). The most recent security fix shipped in 2.8.26.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Brizy version

Enter the Brizy version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Brizy”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Brizy”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.8.26). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Brizy vulnerabilities (latest 25 of 37)

  • Brizy – Page Builder <= 2.8.25 - Missing Authorization

    Missing authorization · CVE-2026-112830

    Affected versions: ≤ 2.8.25

    Fixed in: 2.8.26

    Severity: Medium 5.3 · Disclosed Nov 13, 2026

  • Brizy – Page Builder 2.8.23 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-111844

    Affected versions: ≥ 2.8.23, ≤ 2.8.23

    Fixed in: 2.8.24

    Severity: Medium 6.4 · Disclosed Oct 20, 2026

  • Brizy <= 2.8.18 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'brizy-compiled-sections' Post Meta

    Cross-site scripting (XSS) · CVE-2026-14882

    Affected versions: ≤ 2.8.18

    Fixed in: 2.8.19

    Severity: Medium 6.4 · Disclosed Oct 9, 2026

  • Brizy – Page Builder <= 2.8.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'rootAttributes' Parameter

    Cross-site scripting (XSS) · CVE-2026-2585

    Affected versions: ≤ 2.8.14

    Fixed in: 2.8.15

    Severity: Medium 6.4 · Disclosed Sep 17, 2026

  • Brizy – Page Builder < 2.8.18 - Authenticated (Contributor+) Information Exposure

    Information disclosure · CVE-2026-14195

    Affected versions: < 2.8.18

    Fixed in: 2.8.18

    Severity: Medium 4.3 · Disclosed Aug 1, 2026

  • Brizy - Page Builder <= 2.8.18 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-16068

    Affected versions: ≤ 2.8.18

    Fixed in: 2.8.19

    Severity: Medium 6.4 · Disclosed Jul 27, 2026

  • Brizy - Page Builder <= 2.8.18 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-16069

    Affected versions: ≤ 2.8.18

    Fixed in: 2.8.19

    Severity: Medium 6.4 · Disclosed Jul 27, 2026

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

    Missing authorization · CVE-2026-16070

    Affected versions: ≤ 2.8.18

    Fixed in: 2.8.19

    Severity: Medium 4.3 · Disclosed Jul 27, 2026

  • Brizy – Page Builder <= 2.8.11 - Unauthenticated Stored Cross-Site Scripting via FileUpload Field Value

    Cross-site scripting (XSS) · CVE-2026-5324

    Affected versions: ≤ 2.8.11

    Fixed in: 2.8.12

    Severity: High 7.2 · Disclosed May 1, 2026

  • Brizy <= 2.7.23 - Missing Authorization

    Missing authorization · CVE-2026-32408

    Affected versions: ≤ 2.7.23

    Fixed in: 2.7.24

    Severity: Medium 4.3 · Disclosed Feb 22, 2026

  • Brizy – Page Builder <= 2.7.16 - Authenticated (Contributor+) Sensitive Information Exposure via get_users Function

    Information disclosure · CVE-2025-0969

    Affected versions: ≤ 2.7.16

    Fixed in: 2.7.17

    Severity: Medium 6.5 · Disclosed Dec 12, 2025

  • Brizy <= 2.7.12 - Missing Authorization

    Missing authorization · CVE-2025-58594

    Affected versions: ≤ 2.7.12

    Fixed in: 2.7.13

    Severity: Medium 4.3 · Disclosed Sep 3, 2025

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

    Arbitrary file upload · CVE-2025-4370

    Affected versions: ≤ 2.6.20

    Fixed in: 2.6.21

    Severity: Medium 5.3 · Disclosed Jul 28, 2025

  • Brizy <= 2.7.7 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-32198

    Affected versions: ≤ 2.7.7

    Fixed in: 2.7.8

    Severity: Medium 6.4 · Disclosed Apr 4, 2025

  • Brizy – Page Builder <= 2.6.8 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload

    Cross-site scripting (XSS) · CVE-2024-10322

    Affected versions: ≤ 2.6.8

    Fixed in: 2.6.9

    Severity: Medium 6.4 · Disclosed Feb 12, 2025

  • Brizy – Page Builder <= 2.6.4 - Authenticated (Contributor+) Arbitrary File Upload via storeUploads

    Arbitrary file upload · CVE-2024-10960

    Affected versions: ≤ 2.6.4

    Fixed in: 2.6.5

    Severity: Critical 9.9 · Disclosed Feb 11, 2025

  • Brizy – Page Builder <= 2.5.1 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2024-6254

    Affected versions: ≤ 2.5.1

    Fixed in: 2.5.2

    Severity: Medium 4.3 · Disclosed Aug 7, 2024

  • Brizy – Page Builder <= 2.4.44 - Authenticated (Contributor+) Arbitrary File Upload

    Arbitrary file upload · CVE-2024-3242

    Affected versions: ≤ 2.4.44

    Fixed in: 2.4.45

    Severity: High 8.8 · Disclosed Jul 17, 2024

  • Brizy – Page Builder <= 2.4.44 - Missing Authorization to Authenticated (Contributor+) Post Modification

    Missing authorization · CVE-2024-1937

    Affected versions: ≤ 2.4.44

    Fixed in: 2.4.45

    Severity: High 7.1 · Disclosed Jul 15, 2024

  • Brizy – Page Builder <= 2.4.43 - Authenticated (Contributor+) Store Cross-Site Scripting via Widget Link To URL

    Cross-site scripting (XSS) · CVE-2024-3667

    Affected versions: ≤ 2.4.43

    Fixed in: 2.4.44

    Severity: High 7.4 · Disclosed Jun 4, 2024

  • Brizy – Page Builder <= 2.4.43 - Unauthenticated Stored Cross-Site Scripting via Form

    Cross-site scripting (XSS) · CVE-2024-2087

    Affected versions: ≤ 2.4.43

    Fixed in: 2.4.44

    Severity: High 7.2 · Disclosed Jun 4, 2024

  • Brizy – Page Builder <= 2.4.43 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom Attributes

    Cross-site scripting (XSS) · CVE-2024-1161

    Affected versions: ≤ 2.4.43

    Fixed in: 2.4.44

    Severity: Medium 6.4 · Disclosed Jun 4, 2024

  • Brizy – Page Builder <= 2.4.43 - Authenticated(Contributor+) Stored Cross-Site Scripting via Form Functionality

    Cross-site scripting (XSS) · CVE-2024-1164

    Affected versions: ≤ 2.4.43

    Fixed in: 2.4.44

    Severity: Medium 6.4 · Disclosed Jun 4, 2024

  • Brizy – Page Builder <= 2.4.43 - Missing Authorization

    Missing authorization · CVE-2024-3711

    Affected versions: ≤ 2.4.43

    Fixed in: 2.4.44

    Severity: Medium 4.3 · Disclosed May 22, 2024

  • Brizy – Page Builder <= 2.4.41 - Authenticated(Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-1940

    Affected versions: ≤ 2.4.41

    Fixed in: 2.4.42

    Severity: High 7.1 · Disclosed May 6, 2024

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 13, 2026.

Most common weaknesses in Brizy

Cross-site scripting (XSS)

18 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

8 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Arbitrary file upload

5 issues

An attacker can upload a malicious file disguised as an image or document. Once it is on the server, it can be used to take over the site.

Frequently asked questions

Is Brizy safe to use?

Brizy is a well-known plugin with 60,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.8.26) and turn on automatic updates.

How do I find which version of Brizy my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesBrizy on WordPress.org