Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account on target site
-
DeliveryInject script via rootAttributes when editing page
-
ExploitPayload stored unsanitized in page content
-
ExecutionHigher-privileged user views/previews page
-
PersistScript executes in their admin session
-
ImpactSteal session or perform privileged actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account with Contributor-level role or higher on the target WordPress site running Brizy - Page Builder version 2.8.14 or earlier; the attacker injects the payload via the 'rootAttributes' parameter during page editing. Execution is deferred and conditional: the malicious script only fires when a user (typically a reviewing editor or administrator) subsequently accesses or previews the injected page, so no direct user interaction is needed by the attacker but a victim page view is required for impact. The Contributor authentication gate is the primary limiting factor - sites that do not expose Contributor (or higher) accounts to untrusted parties face little practical exposure. |
| Impact | This is a moderate-severity, authenticated stored XSS whose real-world risk is meaningfully constrained by its privilege requirement. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N = 6.4) is internally consistent with the description: network-reachable, low complexity, but requiring Contributor-level (PR:L) authenticated access, with scope-change (S:C) reflecting script execution in a victim's browser context and limited (C:L/I:L) impact. No EPSS score, no CISA KEV listing, and no public exploit code are present in the supplied intelligence, so this is 'no public exploit identified at time of analysis' rather than an actively-exploited priority. The dominant limiting factor is the trust boundary: an attacker needs a valid Contributor account, which on most sites is a semi-trusted role, making this primarily a privilege-escalation lever (Contributor → executing JS in an Editor/Admin browser when they preview or view the injected page) rather than a mass-exploitable unauthenticated flaw. Treat as a routine 'patch on next maintenance cycle' item unless the site grants Contributor accounts to untrusted users, where it rises to a genuine account-takeover / admin-session-theft concern. No conflicting signals: CVSS network vector matches the WordPress admin-over-HTTP delivery described. |
| Exploit ScenarioDerived | An attacker holding a Contributor account on a Brizy-powered WordPress site edits a page and injects a malicious script payload through the 'rootAttributes' parameter, which the plugin stores without adequate sanitization or output escaping. When a higher-privileged user (editor or administrator) later previews or opens that page in wp-admin, the script executes in their authenticated browser session, enabling session/cookie theft, admin-action forgery, or persistence. No public proof-of-concept is referenced in the supplied data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Authenticated stored cross-site scripting (XSS) in the Brizy Page Builder plugin for WordPress versions up to and including 2.8.14 allows attackers with Contributor-level access or higher to inject arbitrary web scripts via the rootAttributes parameter, which execute when a victim views the affected page. The vulnerability requires authentication and a subsequent page view by another user, and no public exploit has been identified at time of analysis. The CVSS score is 6.4 with a scope change, reflecting limited confidentiality and integrity impact.
RemediationAI
Upstream fix available (changeset 3565838); released patched version not independently confirmed. Site administrators should update the Brizy Page Builder plugin to the latest version, which should include the fix from changeset 3565838, and verify the installed version. If an update is not yet available, restrict the ability to create or edit pages to trusted users only, or remove Contributor-level accounts and above from untrusted parties. Additionally, consider using a web application firewall (WAF) to block XSS payloads targeting the rootAttributes parameter, though this is a compensating control and may not fully mitigate the issue. Monitor the Wordfence advisory for updated version information.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a stored XSS (CWE-79) in the Brizy Page Builder WordPress plugin, caused by insufficient input sanitization and output escaping of the 'rootAttributes' parameter. According to the CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, the attack is network-based, low complexity, requires low privileges (Contributor+), and no user interaction from the attacker's perspective, though a victim must view the page. The scope change (S:C) indicates the vulnerable component affects resources beyond its security scope, such as executing script in the context of other users. The plugin is installed on WordPress sites, and the vulnerability affects all versions up to 2.8.14.
Know when Brizy gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Network-delivered via WordPress admin, low complexity, but requires an authenticated Contributor account (PR:L); stored XSS crosses into a victim's browser context (S:C) with limited confidentiality/integrity impact and no availability effect.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The Brizy - Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘rootAttributes’ parameter in all versions up to, and including, 2.8.14 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
The Brizy plugin for WordPress is vulnerable to authorization bypass due to a incorrect capability check on the is_admin
The Unyson WordPress plugin before 2.7.27 does not sanitise and escape a parameter before outputting it back in the page
Stored cross-site scripting in the Brizy WordPress plugin before 2.8.19 allows any authenticated user with Contributor r
The Brizy - Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validatio
The Brizy - Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validatio
The Brizy - Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file extension vali
The Brizy WordPress plugin before 2.4.2 does not sanitise and escape some element content, which could allow users with
The Brizy WordPress plugin before 2.4.2 does not sanitise and escape some element URL, which could allow users with a ro
The Brizy Page Builder plugin <= 2.3.11 for WordPress was vulnerable to stored XSS by lower-privileged users such as a s
The Brizy Page Builder plugin <= 2.3.11 for WordPress allowed authenticated users to upload executable files to a locati
The Brizy - Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the form name values in a
Stored XSS in the Brizy WordPress plugin (all versions before 2.8.19) allows authenticated Author-level users to inject
EUVD-2026-82607
GHSA-9fpv-wc48-8pf3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB