Brizy - Page Builder <= 2.8.18 - Authenticated (Author+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.8.19
- Affected Plugin
- Brizy – Page Builder
- Affected Version
<= 2.8.18- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-16068
At a glance
CVE-2026-16068 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Brizy WordPress plugin, affecting versions <= 2.8.18. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author 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 Stored Cross-Site Scripting in versions up to, and including, 2.8.18 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Brizy <= 2.8.18 takes an account at Author level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. 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?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Brizy 2.8.19 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Brizy – Page Builder
- 9.9CVE-2024-10960: Brizy – Page Builder <= 2.6.4 Arbitrary File Upload
CVE-2024-10960 - 8.8CVE-2024-3242: Brizy – Page Builder <= 2.4.44 Arbitrary File Upload
CVE-2024-3242 - 8.8CVE-2024-1311: Brizy – Page Builder <= 2.4.40 Arbitrary File Upload
CVE-2024-1311 - 8.8CVE-2021-38346: Brizy Page Builder File Upload and Path Traversal
CVE-2021-38346 - 7.4CVE-2020-36714: Brizy Authorization Bypass to Settings Updates
CVE-2020-36714 - 7.1CVE-2024-1937: Brizy Authenticated (Contributor+) Post Modification
CVE-2024-1937 - 7.1CVE-2021-38345: Brizy Page Builder Incorrect Authorization Checks
CVE-2021-38345 - 6.5CVE-2025-0969: Brizy – Page Builder <= 2.7.16 Info Exposure
CVE-2025-0969
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C