Attack Chain

1. An unauthenticated attacker crafts a malicious payload containing JavaScript code.
2. The attacker submits this payload through a Brizy form on the WordPress site, exploiting the missing nonce verification in the submit_form() function.
3. The handleFileTypeFields() function fails to properly sanitize or overwrite the attacker-supplied values when no file is attached to the form submission.
4. The injected payload, now stored in the WordPress database, bypasses initial htmlentities() encoding due to later html_entity_decode().
5. An administrator logs into the WordPress dashboard and navigates to the “Leads” page to view form submissions.
6. The form-data.php template retrieves the stored malicious payload from the database.
7. The payload is outputted directly within the href attribute of an HTML element without proper escaping using esc_url().
8. The injected JavaScript code executes within the administrator’s browser, potentially performing actions such as stealing cookies or redirecting the administrator to a malicious site.

Impact

Successful exploitation of this vulnerability allows an unauthenticated attacker to execute arbitrary JavaScript code in the context of a logged-in administrator’s browser. This could lead to a full compromise of the WordPress site, including the ability to create new administrative accounts, modify existing content, inject malware into the site’s pages, or steal sensitive data. The impact is significant, as it requires no user interaction beyond an administrator viewing the form submissions within the Brizy plugin.

Recommendation

• Upgrade the Brizy – Page Builder plugin to the latest version to patch CVE-2026-5324.
• Deploy the Sigma rule “Detect Brizy WordPress Plugin XSS Attempt via HTTP Request” to identify potential exploitation attempts in web server logs.
• Review the form-data.php template and implement proper output escaping using esc_url() for all user-supplied data to prevent XSS, as mentioned in the vulnerability description.