CVE-2026-15047

s2Member <= 260804 - Authenticated (Contributor+) Stored Cross-Site Scripting

2026-08-07 00:00
Muni Nitish Kumar Yaddala

Strategic Overview

Status
Patched in 260805
Affected Plugin
s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions
Affected Version
<= 260804
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2026-15047
View all s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions vulnerabilities

At a glance

CVE-2026-15047 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the s2Member WordPress plugin, affecting versions <= 260804. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 260805; sites on affected versions should update now. Disclosed August 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The s2Member plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 260804 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

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

Reaching this weakness in s2Member <= 260804 takes an account at Contributor level or above. 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 260805: builds <= 260804 are affected, anything from 260805 onward is not.

Remediation

Update to version 260805, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: s2Member 260805 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-15047https://www.wordfence.com/threat-intel/vulnerabilities/id/3ac8a509-e54b-40e7-9fd8-4aef03168827https://nvd.nist.gov/vuln/detail/CVE-2026-15047

Related records

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