CVE-2019-12566

WP Statistics <= 12.6.5 - Stored Cross-Site Scripting

2019-05-31 00:00
Anonymous

Strategic Overview

Status
Patched in 12.6.6.1
Affected Version
<= 12.6.5
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2019-12566
View all WP Statistics – Simple, privacy-friendly Google Analytics alternative vulnerabilities

At a glance

CVE-2019-12566 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Statistics WordPress plugin, affecting versions <= 12.6.5. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 12.6.6.1; sites on affected versions should update now. Disclosed May 2019.

Vulnerability Overview

The WP Statistics plugin through 12.6.5 for Wordpress has stored XSS in includes/class-wp-statistics-pages.php. This is related to an account with the Editor role creating a post with a title that contains JavaScript, to attack an admin user.

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 interaction from a victim user.

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

Reaching this weakness in WP Statistics <= 12.6.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 WP Statistics the fix is 12.6.6.1: builds <= 12.6.5 are affected, anything from 12.6.6.1 onward is not.

Remediation

Update to version 12.6.6.1, or a newer patched version

How does WordSec protect against this?

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