Skip to main content
CVE-2024-51815VulnerabilityPublished Updated

CVE-2024-51815: s2Member (WordPress plugin) · Code Injection

Affects s2Member (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.0 Critical.

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.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 6 Dec 2024

  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

Affected software

ProductAffectedFixed in
Cristián Lávaque s2MemberAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is released, users should monitor for updates from Cristián Lávaque or the s2Member project. Consider applying temporary mitigations such as restricting network access to the affected plugin or disabling it if feasible.

Description

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

References

Community reviews

Loading reviews…