WPBakery Page Builder for WordPress (formerly Visual Composer) <= 4.7.3 - Multiple Cross-Site Scripting Issues

2015-02-10 00:00
Anonymous

Strategic Overview

Status
Patched in 4.7.4
Affected Plugin
WPBakery Page Builder
Affected Version
< 4.7.4
CVSS
7.2High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all WPBakery Page Builder vulnerabilities

At a glance

This record tracks a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WPBakery Page Builder WordPress plugin, affecting versions < 4.7.4. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.7.4; sites on affected versions should update now. Disclosed February 2015.

Vulnerability Overview

The WPBakery Page Builder for WordPress plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 4.7.3 that made it possible for attackers to inject arbitrary web scripts into pages.

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 privileges on the target site, and no interaction from a victim user.

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

Reaching this weakness in WPBakery Page Builder < 4.7.4 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 WPBakery Page Builder the fix is 4.7.4: builds < 4.7.4 are affected, anything from 4.7.4 onward is not.

Remediation

Update to version 4.7.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPBakery Page Builder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPBakery Page Builder 4.7.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/b94facce-975f-4080-ad67-95d282b28d0d

Related records

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