CVE-2026-16068 Brizy - Page Builder < 2.8.19 - Author+ Stored XSS via brizy_set_project Global Project Code Asset
Authenticated Authors can inject malicious JavaScript into global project settings, leading to stored XSS that executes in visitors' browsers, including administrators.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-16068?
CVE-2026-16068 is a low-severity cross-site scripting vulnerability in Unknown Brizy, published on 4 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-16068?
How do I fix CVE-2026-16068?
No fix has been published for CVE-2026-16068 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-16068 being exploited?
There is no known exploitation of CVE-2026-16068 in the wild and no public exploit code.
Sources
Also known as GHSA-3qrh-q76v-gc9c.