CVE-2015-6238

Google Analyticator <= 6.4.9.5 - Cross-Site Scripting

2015-08-24 00:00
Anonymous

Strategic Overview

Status
Patched in 6.4.9.6
Affected Plugin
Analyticator
Affected Version
< 6.4.9.6
CVSS
4.7Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2015-6238
View all Analyticator vulnerabilities

At a glance

CVE-2015-6238 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Analyticator WordPress plugin, affecting versions < 6.4.9.6. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 6.4.9.6; sites on affected versions should update now. Disclosed August 2015.

Vulnerability Overview

Multiple cross-site scripting (XSS) vulnerabilities in the Google Analyticator plugin before 6.4.9.6 for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) ga_adsense, (2) ga_admin_disable_DimentionIndex, (3) ga_downloads_prefix, (4) ga_downloads, or (5) ga_outbound_prefix parameter in the google-analyticator page to wp-admin/admin.php.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.

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

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

Remediation

Update to version 6.4.9.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Analyticator: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Analyticator 6.4.9.6 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