CVE-2026-5324: Brizy – Page Builder <= 2.8.11 - Unauthenticated Stored Cross-Site Scripting via FileUpload Field Value
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 htmlentitydecode() followed by unescaped output in the admin view. The submitform() 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, htmlentitydecode() reverses this on display (form-entries.php:79). The form-data.php template outputs FileUpload values directly in href attributes without escurl(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the form Leads page.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5324?
The severity of CVE-2026-5324 is considered critical due to the potential for unauthenticated stored cross-site scripting attacks.
How do I fix CVE-2026-5324?
To fix CVE-2026-5324, update the Brizy – Page Builder plugin to version 2.8.12 or later.
What types of attacks can CVE-2026-5324 facilitate?
CVE-2026-5324 can facilitate unauthenticated stored cross-site scripting attacks, allowing attackers to inject malicious scripts.
Who is affected by CVE-2026-5324?
Users of Brizy – Page Builder versions 2.8.11 and earlier are affected by CVE-2026-5324.
Is authentication required to exploit CVE-2026-5324?
No, CVE-2026-5324 can be exploited without authentication, making it particularly dangerous.