CVE-2026-5324
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Brizy Page Builder plugin fails to validate nonces on unauthenticated form submissions and incorrectly handles FileUpload fields, allowing arbitrary script injection. User-supplied values in FileUpload fields persist even when no file is uploaded, and while htmlentities() protects storage, html_entity_decode() reverses this protection on display in form-entries.php:79. Additionally, form-data.php outputs FileUpload values in href attributes without esc_url() escaping, enabling stored XSS execution when administrators view form leads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Brizy Page Builder plugin installationCheck the WordPress plugins directory or wp-content/plugins/ folder for the 'brizy' folder. Look for a main plugin file (such as brizy.php) and inspect its header for the version number.Affected if The plugin is not installed or the version cannot be determined.
-
Compare installed version to known vulnerable releasesReview the plugin version header against any official vulnerability disclosure. Since specific version ranges are not provided in this CVE, note that versions prior to a security patch releasing the fix are potentially affected.Affected if The installed version predates the security fix for this vulnerability.
-
Inspect form-entries.php for unsafe html_entity_decodeLocate the file form-entries.php in the plugin directory and examine line 79 (or nearby lines) for the use of html_entity_decode() on user-supplied data.Affected if html_entity_decode() is present and applied to stored form values without additional escaping.
-
Inspect form-data.php for missing esc_url on href attributesLocate form-data.php in the plugin directory and search for href attributes that output FileUpload field values. Verify whether esc_url() wrapping is applied to those outputs.Affected if FileUpload values appear in href attributes without esc_url() escaping.
-
Confirm presence of FileUpload fields in any formsSearch the WordPress database or plugin files for form configurations containing FileUpload field definitions. Check if any forms accept file uploads.Affected if Forms with FileUpload fields are defined and active on the site.
-
Determine if unauthenticated form submissions are acceptedReview the plugin's form handling logic for nonce verification. Check if form submission endpoints accept requests without authentication or valid nonce tokens.Affected if Form submissions process without requiring authenticated sessions or valid nonce validation.
If the Brizy Page Builder plugin is installed, contains the vulnerable php files with the described code patterns, and exposes forms with FileUpload fields to visitors, the stored XSS can be triggered when administrators view form entries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement nonce verification for all form submissions including unauthenticated requests, properly sanitize FileUpload field handling to discard user-supplied values when no file is attached, remove html_entity_decode() or apply proper escaping on output, and add esc_url() to all href attribute outputs.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5324 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data