Brizy Page Builder <= 2.3.11 - Incorrect Authorization Checks Allowing Post Modification
Strategic Overview
- Status
- Patched in 1.0.126
- Affected Plugin
- Brizy – Page Builder
- Affected Version
1.0.125 – 2.3.11 · 2 branches- CVSS
- 7.1High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-38345
At a glance
CVE-2021-38345 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Brizy WordPress plugin, affecting versions 1.0.125 – 2.3.11 · 2 branches. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high integrity impact). The issue is fixed in version 1.0.126; sites on affected versions should update now. Disclosed October 2020, reported by Ram.
Vulnerability Overview
The Brizy Page Builder plugin <= 2.3.11 for WordPress used an incorrect authorization check that allowed any logged-in user accessing any endpoint in the wp-admin directory to modify the content of any existing post or page created with the Brizy editor. An identical issue was found by another researcher in Brizy <= 1.0.125 and fixed in version 1.0.126, but the vulnerability was reintroduced in version 1.0.127.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Brizy 1.0.125 – 2.3.11 · 2 branches takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Brizy the fix is 1.0.126: builds 1.0.125 – 2.3.11 · 2 branches are affected, anything from 1.0.126 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 1.0.126, 2.3.12
How does WordSec protect against this?
The attempt arrives as an ordinary request to Brizy: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Brizy 1.0.126 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Brizy – Page Builder
- 9.9CVE-2024-10960: Brizy – Page Builder <= 2.6.4 Arbitrary File Upload
CVE-2024-10960 - 8.8CVE-2024-3242: Brizy – Page Builder <= 2.4.44 Arbitrary File Upload
CVE-2024-3242 - 8.8CVE-2024-1311: Brizy – Page Builder <= 2.4.40 Arbitrary File Upload
CVE-2024-1311 - 8.8CVE-2021-38346: Brizy Page Builder File Upload and Path Traversal
CVE-2021-38346 - 7.4CVE-2020-36714: Brizy Authorization Bypass to Settings Updates
CVE-2020-36714 - 7.1CVE-2024-1937: Brizy Authenticated (Contributor+) Post Modification
CVE-2024-1937 - 6.5CVE-2025-0969: Brizy – Page Builder <= 2.7.16 Info Exposure
CVE-2025-0969 - 6.5Brizy - Page Builder < 1.0.114 Settings Update
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C