Wordfence < 3.3.7 - Reflected Cross-Site Scripting

2012-10-19 00:00
Eugene Dokukin

Strategic Overview

Status
Patched in 3.3.7
Affected Plugin
Wordfence Security – Firewall, Malware Scan, and Login Security
Affected Version
< 3.3.7
CVSS
6.1Medium
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 < 3.3.7. 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 3.3.7; sites on affected versions should update now. Disclosed October 2012, reported by Eugene Dokukin.

Vulnerability Overview

The Wordfence plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘email’ parameter in versions before 3.3.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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')

Wordfence Security < 3.3.7 carries this weakness at email, 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 Wordfence Security the fix is 3.3.7: builds < 3.3.7 are affected, anything from 3.3.7 onward is not.

Remediation

Update to version 3.3.7, 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 3.3.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/bdc39e21-f39c-4581-895a-04e352e9b383

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C