Wordfence Security – Firewall & Malware Scan <= 7.1.13 - Reflected Cross-Site Scripting and Information Disclosure

2018-10-02 00:00
Janek Vind

Strategic Overview

Status
Patched in 7.1.14
Affected Version
< 7.1.14
CVSS
4.7Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all Wordfence Security – Firewall, Malware Scan, and Login Security vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Wordfence Security WordPress plugin, affecting versions < 7.1.14. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 7.1.14; sites on affected versions should update now. Disclosed October 2018, reported by Janek Vind.

Vulnerability Overview

Wordfence before 7.1.14 was vulnerable in certain unusual configurations to Reflected Cross-Site Scripting, as well as full path disclosure and author name disclosure.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.

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

Reaching this weakness in Wordfence Security < 7.1.14 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 Wordfence Security the fix is 7.1.14: builds < 7.1.14 are affected, anything from 7.1.14 onward is not.

Remediation

Update to version 7.1.14, or a newer patched version

How does WordSec protect against this?

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