s2Member (Pro) <= 241114 - Unauthenticated Remote Code Execution
Strategic Overview
- Status
- Patched in 241216
- Affected Plugin
- s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions
- Affected Version
<= 241114- CVSS
- 8.1High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2024-51815
At a glance
CVE-2024-51815 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the s2Member WordPress plugin, affecting versions <= 241114. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 241216; sites on affected versions should update now. Disclosed December 2024, reported by Hakiduck.
Vulnerability Overview
The s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions (Pro) plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 241114. This makes it possible for unauthenticated attackers to execute code on the server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in s2Member <= 241114 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For s2Member the fix is 241216: builds <= 241114 are affected, anything from 241216 onward is not.
Remediation
Update to version 241216, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: s2Member 241216 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Same weakness class
Other vulnerabilities in s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions
- 9.8CVE-2026-1994: s2Member <= 260127 Privilege Escalation
CVE-2026-1994 - 9.1CVE-2024-31237: s2Member <= 240315 Limited Privilege Escalation
CVE-2024-31237 - 8.8CVE-2024-8326: s2Member Info Exposure
CVE-2024-8326 - 8.1CVE-2025-58998: s2Member <= 250701 PHP Object Injection
CVE-2025-58998 - 7.2CVE-2025-32137: s2Member <= 250419 Local File Inclusion
CVE-2025-32137 - 7.2CVE-2011-5082: s2Member® Framework XSS
CVE-2011-5082 - 6.4CVE-2026-15047: s2Member <= 260804 Stored Cross-Site Scripting
CVE-2026-15047 - 6.4CVE-2025-13732: s2Member <= 251005 Stored Cross-Site Scripting
CVE-2025-13732
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C