CVE-2016-10969

SupportFlow <= 0.6 - Stored Cross-Site Scripting via discussion ticket title

2016-06-20 00:00
White Hatter

Strategic Overview

Status
Patched in 0.7
Affected Plugin
SupportFlow
Affected Version
<= 0.6
CVSS
7.2High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2016-10969
View all SupportFlow vulnerabilities

At a glance

CVE-2016-10969 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the SupportFlow WordPress plugin, affecting versions <= 0.6. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.7; sites on affected versions should update now. Disclosed June 2016, reported by White Hatter.

Vulnerability Overview

The supportflow plugin before 0.7 for WordPress has XSS via a discussion ticket title if 'run_wptexturize' is disabled.

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

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

SupportFlow <= 0.6 carries this weakness at run_wptexturize, and reaching it 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 SupportFlow the fix is 0.7: builds <= 0.6 are affected, anything from 0.7 onward is not.

Remediation

Update to version 0.7, or a newer patched version

How does WordSec protect against this?

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