Skip to main content
CVE-2025-62023VulnerabilityPublished Updated

CVE-2025-62023: s2Member (WordPress plugin) · Code Injection

Affects s2Member (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.0 Critical : upgrade to 251005 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 251005
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Upgrade s2Member (WordPress plugin) to 251005.

Affected software

ProductAffectedFixed in
Cristián Lávaques2MemberAffected
  • <251005
Fixed in
  • 251005

AI-suggested

If you cannot patch yet, users should consider disabling or limiting exposure of the affected s2Member plugin to untrusted networks.

Description

Improper Control of Generation of Code ('Code Injection') vulnerability in Cristián Lávaque s2Member s2member.This issue affects s2Member: from n/a through 250905.

References

Community reviews

Loading reviews…