Brizy Authors can inject site-wide frontend JavaScript
Brizy before 2.8.19 does not adequately restrict modification of site-global design data and fails to sanitize part of that data before frontend output. An Author can store arbitrary JavaScript in the global design value, after which the script is served on site pages and executes for visitors, including administrators. The public advisory does not disclose the endpoint, action, parameter, data key or output function.
- Component
- Brizy
- Plugin slug
brizy- Affected
- < 2.8.19
- Safe version
2.8.19- Published
- Aug 04, 2026
This CVE was published Aug 04, 2026 and is one of 34 known issues for this plugin.
Update, patch or deactivate.
Update Brizy to 2.8.19 or later. Review site-global design data for unexpected scripts and invalidate privileged sessions if administrators browsed the affected frontend while malicious data was present.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Brizy WordPress plugin before 2.8.19 does not properly restrict who can modify its site-global design data and does not sanitise part of that data before outputting it, allowing authenticated users with Author-level access and above to store arbitrary JavaScript that is then served unsanitised on the site's front-end pages and executes in the browser of every visitor, including administrators.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N