CVE-2011-5082

s2Member® Framework (Membership, Member Level Roles, Access Capabilities, PayPal Members) < 111220 - Cross-Site Scripting

2012-02-12 00:00
Chris Martin

Strategic Overview

Status
Patched in 111220
Affected Version
< 111220
CVSS
7.2High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2011-5082
View all s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions vulnerabilities

At a glance

CVE-2011-5082 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the s2Member WordPress plugin, affecting versions < 111220. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 111220; sites on affected versions should update now. Disclosed February 2012, reported by Chris Martin.

Vulnerability Overview

Cross-site scripting (XSS) vulnerability in the s2Member Pro plugin before 111220 for WordPress allows remote attackers to inject arbitrary web script or HTML via the s2member_pro_authnet_checkout[coupon] parameter (aka Coupon Code field).

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, and no interaction from a victim user.

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

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

Remediation

Update to version 111220, or a newer patched version

How does WordSec protect against this?

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