MainWP Child <= 2.0.27 - Multiple Cross-Site Scripting

2015-09-07 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0.28
Affected Plugin
MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites
Affected Version
<= 2.0.27
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites vulnerabilities

At a glance

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

Vulnerability Overview

The MainWP Child plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 2.0.27 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser.

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.

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

Reaching this weakness in MainWP Child <= 2.0.27 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 MainWP Child the fix is 2.0.28: builds <= 2.0.27 are affected, anything from 2.0.28 onward is not.

Remediation

Update to version 2.0.28, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/a5a34838-fdc5-4954-9576-abf81cbaac2e

Related records

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