CVE-2017-15811

pootle button <= 1.1.1 - Reflected Cross-Site Scripting

2017-10-12 00:00
Ricardo Sanchez

Strategic Overview

Status
Patched in 1.2.0
Affected Plugin
pootle button
Affected Version
<= 1.1.1
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2017-15811
View all pootle button vulnerabilities

At a glance

CVE-2017-15811 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the pootle button WordPress plugin, affecting versions <= 1.1.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 1.2.0; sites on affected versions should update now. Disclosed October 2017, reported by Ricardo Sanchez.

Vulnerability Overview

The Pootle Button plugin before 1.2.0 for WordPress has XSS via the assets_url parameter in assets/dialog.php, exploitable via wp-admin/admin-ajax.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.

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

Reaching this weakness in pootle button <= 1.1.1 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 pootle button the fix is 1.2.0: builds <= 1.1.1 are affected, anything from 1.2.0 onward is not.

Remediation

Update to version 1.2.0, or a newer patched version

How does WordSec protect against this?

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