# 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.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N`)
- **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 available:** No
- **Published:** 4 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-3qrh-q76v-gc9c

## 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 (Improper Neutralization of Input During Web Page Generation)

## 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.

## Is CVE-2026-16068 being exploited?

There is no known exploitation of CVE-2026-16068 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16068 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-16068 in the wild and no public exploit code.

Affected product: Unknown Brizy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16068/ (Markdown: https://insights.sbomify.com/CVE-2026-16068/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16068
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16068
- OSV: https://osv.dev/vulnerability/CVE-2026-16068

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16068/
Summaries are generated and may contain mistakes; the official description above is the record.