Skip to main content
VulnerabilityPublished

CVE-2026-86596: s2Member (WordPress plugin) · Code Injection

Affects s2Member (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 2 Nov 2026, 21:58 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.19.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
clavaques2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access SubscriptionsAffected
  • <=260927
Fixed in–

AI-suggested

Users should restrict access to trusted users only and consider disabling or removing the s2Member plugin until a vendor-provided fix is available. Monitor the vendor's advisory channels for updates. Since this is a code injection vulnerability requiring authenticated access, limiting user privileges can reduce risk.

Description

The s2Member WordPress plugin is vulnerable to remote code execution via the 'item_name' parameter due to insufficient sanitization of PHP code tags. Authenticated users with custom-level access or higher can exploit this to execute arbitrary code on the server. This affects all versions up to and including 260927. The vulnerability arises from the strip_php_tags_deep() function only removing literal '<?' sequences, allowing attackers to reconstruct valid PHP openers after interpolation in email templates.

References

Community reviews

Loading reviews…