CVE-2018-10309

Responsive Cookie Consent < 1.8 - Cross-Site Scripting

2018-04-24 00:00
B0UG

Strategic Overview

Status
Patched in 1.8
Affected Version
< 1.8
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2018-10309
View all Responsive Cookie Consent vulnerabilities

At a glance

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

Vulnerability Overview

The Responsive Cookie Consent plugin before 1.8 for WordPress mishandles number fields, leading to XSS.

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

Remediation

Update to version 1.8, or a newer patched version

How does WordSec protect against this?

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