CVE-2021-38344

Brizy - Page Builder <= 2.3.11 - Stored Cross-Site Scripting

2021-10-13 00:00
Ram

Strategic Overview

Status
Patched in 2.3.12
Affected Plugin
Brizy – Page Builder
Affected Version
<= 2.3.11
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-38344
View all Brizy – Page Builder vulnerabilities

At a glance

CVE-2021-38344 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Brizy WordPress plugin, affecting versions <= 2.3.11. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.3.12; sites on affected versions should update now. Disclosed October 2021, reported by Ram.

Vulnerability Overview

The Brizy Page Builder plugin <= 2.3.11 for WordPress was vulnerable to stored XSS by lower-privileged users such as a subscribers. It was possible to add malicious JavaScript to a page by modifying the request sent to update the page via the brizy_update_item AJAX action and adding JavaScript to the data parameter, which would be executed in the session of any visitor viewing or previewing the post or page.

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.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Brizy <= 2.3.11 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 2.3.12: builds <= 2.3.11 are affected, anything from 2.3.12 onward is not.

Remediation

Update to version 2.3.12, or a newer patched version

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 2.3.12 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-38344https://www.wordfence.com/threat-intel/vulnerabilities/id/8774f448-ba63-428c-8a82-b229718fdd10https://nvd.nist.gov/vuln/detail/CVE-2021-38344

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C