CVE-2022-2040

Brizy Page Builder <= 2.4.1 - Authenticated Stored Cross-Site Scripting via Element URL

2022-06-21 00:00
Vishnupriya Ilango

Strategic Overview

Status
Patched in 2.4.2
Affected Plugin
Brizy – Page Builder
Affected Version
< 2.4.2
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-2040
View all Brizy – Page Builder vulnerabilities

At a glance

CVE-2022-2040 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Brizy WordPress plugin, affecting versions < 2.4.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.4.2; sites on affected versions should update now. Disclosed June 2022, reported by Vishnupriya Ilango.

Vulnerability Overview

The Brizy WordPress plugin before 2.4.2 does not sanitise and escape some element URL, which could allow users with a role as low as Contributor to perform Stored Cross-Site Scripting attacks

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

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

Reaching this weakness in Brizy < 2.4.2 takes any authenticated account. 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.4.2: builds < 2.4.2 are affected, anything from 2.4.2 onward is not.

Remediation

Update to version 2.4.2, 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.4.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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