s2Member · Security record

Is s2Member safe?

No known vulnerability affects the current version (261106). 16 issues were found in earlier versions and fixed, the latest disclosed on Oct 27, 2026.

Checked 3 days ago against the WPVulnerability database, for version 261106.

How it’s looked after

Last release: Nov 6, 2026 (3 days ago)
Releases in the last year: 19
Tested up to: WordPress 7.2
Support resolved: 1 of 1 threads in two months
Active installs: 8K+

16 known vulnerabilities

4 critical
4 high
5 medium
3 not rated

None affects the current version.

Disclosed each year

20121
20244
20255
20266

Every known vulnerability in s2Member

Newest first, with any that affect the current version at the top.

critical
Unauthenticated Remote Code Execution via 'item_name' IPN Parameter
Fixed in 261001 · CVE-2026-86596 · Oct 27, 2026 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via 'date_format' Shortcode Attribute
Fixed in 261017 · CVE-2026-109972 · Sep 24, 2026 · Wordfence
high
Unauthenticated Remote Code Execution via 'first_name' Parameter in PayPal Proxy Return
Fixed in 260829 · CVE-2026-19804 · Aug 7, 2026 · Wordfence
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 260805 · CVE-2026-15047 · Aug 7, 2026 · Wordfence
Unauthenticated Privilege Escalation via Account Takeover
Fixed in 260215 · CVE-2026-1994 · Feb 18, 2026 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
Fixed in 260101 · CVE-2025-13732 · Feb 18, 2026 · Wordfence
critical
Unauthenticated Remote Code Execution
Fixed in 251005 · CVE-2025-62023 · Oct 1, 2025 · Wordfence
critical
Unauthenticated PHP Object Injection
Fixed in 250905 · CVE-2025-58998 · Aug 21, 2025 · Wordfence
medium
Authenticated (Administrator+) Local File Inclusion
Fixed in 250424 · CVE-2025-32137 · Apr 4, 2025 · Wordfence
high
Reflected Cross-Site Scripting
Fixed in 250214 · CVE-2025-26879 · Feb 22, 2025 · Wordfence
medium
Reflected Cross-Site Scripting
Fixed in 250214 · CVE-2024-11376 · Feb 17, 2025 · Wordfence
high
Authenticated (Contributor+) Sensitive Information Exposure
Fixed in 241216 · CVE-2024-8326 · Dec 16, 2024 · Wordfence
critical
Unauthenticated Remote Code Execution
Fixed in 241216 · CVE-2024-51815 · Dec 2, 2024 · Wordfence
high
Limited Privilege Escalation
Fixed in 240325 · CVE-2024-31237 · Apr 5, 2024 · Wordfence
medium
Information Exposure
Fixed in 240315 · CVE-2024-0899 · Mar 18, 2024 · Wordfence
Cross-Site Scripting
Fixed in 111220 · CVE-2011-5082 · Feb 12, 2012 · Wordfence

Questions about s2Member’s security

Is s2Member safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep s2Member updated: most attacks target sites that haven’t updated.

Does s2Member have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 16 older issues, fixed in earlier versions, so keep s2Member up to date.

Is s2Member still maintained?

Yes. Its last release was 3 days ago. Its authors resolved 1 of the 1 support threads opened in the last two months.

Is s2Member compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.2, ahead of the current 7.1.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.