CVE-2014-100018

Unconfirmed < 1.2.5 - Reflected Cross-Site Scripting

2014-04-11 00:00
Mallory Adams

Strategic Overview

Status
Patched in 1.2.5
Affected Plugin
Unconfirmed
Affected Version
< 1.2.5
CVSS
7.1High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2014-100018
View all Unconfirmed vulnerabilities

At a glance

CVE-2014-100018 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Unconfirmed WordPress plugin, affecting versions < 1.2.5. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.5; sites on affected versions should update now. Disclosed April 2014, reported by Mallory Adams.

Vulnerability Overview

Cross-site scripting (XSS) vulnerability in the Unconfirmed plugin before 1.2.5 for WordPress allows remote attackers to inject arbitrary web script or HTML via the s parameter in the unconfirmed page to wp-admin/network/users.php.

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 Unconfirmed < 1.2.5 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 Unconfirmed the fix is 1.2.5: builds < 1.2.5 are affected, anything from 1.2.5 onward is not.

Remediation

Update to version 1.2.5, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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