CVE-2011-3841

WP Symposium <= 11.11.26 - Cross-Site Scripting

2014-08-01 00:00
Simon Goodchild

Strategic Overview

Status
Patched in 11.12.08
Affected Plugin
WP Symposium
Affected Version
<= 11.11.26
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2011-3841
View all WP Symposium vulnerabilities

At a glance

CVE-2011-3841 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Symposium WordPress plugin, affecting versions <= 11.11.26. 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 11.12.08; sites on affected versions should update now. Disclosed August 2014, reported by Simon Goodchild.

Vulnerability Overview

Cross-site scripting (XSS) vulnerability in uploadify/get_profile_avatar.php in the WP Symposium plugin before 11.12.08 for WordPress allows remote attackers to inject arbitrary web script or HTML via the uid parameter.

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 WP Symposium <= 11.11.26 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 WP Symposium the fix is 11.12.08: builds <= 11.11.26 are affected, anything from 11.12.08 onward is not.

Remediation

Update to version 11.12.08, or a newer patched version

How does WordSec protect against this?

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