Quick answers
- Is CVE-2026-16068 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16068 being exploited in the wild.
- How severe is CVE-2026-16068?
- Low severity, with a CVSS score of 3.5, published 4 August 2026.
- Which products and versions are affected?
- Brizy before 2.8.19.
- Is there a fix for CVE-2026-16068?
- A patch was published on 2026-08-04: Fixed in version 2.8.19 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16068 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16068?
- Check whether you run Brizy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored cross-site scripting (XSS) flaw in the brizy_set_project AJAX action. The plugin does not properly restrict who can modify the site-global project data (accessible to Author-level users via the publish_posts capability) and fails to sanitize arbitrary JavaScript stored in the compiled styles field before outputting it on the front-end. An authenticated Author can obtain a valid nonce via the heartbeat endpoint, call brizy_set_project without the 'post' parameter to target the global project, and inject raw script tags into the compiled styles that are served unescaped in the HTML head to all visitors. The vulnerability affects versions before 2.8.19 and was fixed in that version.
Affected products
- Brizy Brizy before 2.8.19
Timeline
- 2026-07-27: disclosed
- 2026-08-04: patched: Fixed in version 2.8.19
- 2026-08-04: advisory