CVE-2018-10371

WF Cookie Consent <= 1.1.3 - Cross-Site Scripting

2018-05-01 00:00
B0UG

Strategic Overview

Status
Patched in 1.1.4
Affected Plugin
WF Cookie Consent
Affected Version
< 1.1.4
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2018-10371
View all WF Cookie Consent vulnerabilities

At a glance

CVE-2018-10371 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WF Cookie Consent WordPress plugin, affecting versions < 1.1.4. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.4; sites on affected versions should update now. Disclosed May 2018, reported by B0UG.

Vulnerability Overview

An issue was discovered in the wunderfarm WF Cookie Consent plugin 1.1.3 for WordPress. A persistent cross-site scripting vulnerability has been identified in the web interface of the plugin that allows the execution of arbitrary HTML/script code to be executed in a victim's web browser via a page title.

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 WF Cookie Consent < 1.1.4 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 WF Cookie Consent the fix is 1.1.4: builds < 1.1.4 are affected, anything from 1.1.4 onward is not.

Remediation

Update to version 1.1.4, or a newer patched version

How does WordSec protect against this?

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