dbcve.org
S2memberWordPress extension

CVE-2024-12562

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-15
Fix available
A fix is available. Upgrade to 250214 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The s2Member Pro plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 241216 via deserialization of untrusted input from the 's2member_pro_remote_op' vulnerable parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The s2Member Pro WordPress plugin is vulnerable to PHP Object Injection via deserialization of untrusted input in the 's2member_pro_remote_op' parameter. Unauthenticated attackers can inject arbitrary PHP objects, and while the plugin itself lacks a POP chain, additional plugins or themes on the target system could provide one to achieve remote code execution, file deletion, or data exfiltration.

MitigationUpdate s2Member Pro to the latest patched version immediately. If no patch is available, disable the plugin and audit the WordPress environment for other plugins/themes that could provide a POP chain.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
S2memberWordPress extension
Affected:< 250214

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify s2Member Pro plugin is installed
    Check the WordPress plugins directory or access wp-admin/plugins.php to list installed plugins and look for 's2Member Pro'
    Affected if s2Member Pro appears in the installed plugins list
  2. Check installed s2Member Pro version
    In WordPress admin, go to Plugins > Installed Plugins > s2Member Pro and read the version number displayed beneath the plugin name; compare it to the affected range of versions before 250214
    Affected if The installed version is lower than 250214 (e.g., 250101, 240912, etc.)
  3. Confirm the plugin is active
    In WordPress admin at wp-admin/plugins.php, verify that s2Member Pro shows as 'Active' rather than 'Inactive' or 'Must-Use'
    Affected if s2Member Pro is active and the version is below 250214
  4. Inspect HTTP request logs for the vulnerable parameter
    Review web server access logs (Apache, Nginx) or WordPress audit logs for requests containing 's2member_pro_remote_op' as a parameter name, especially from unauthenticated sources
    Affected if Any HTTP requests to the site contain the s2member_pro_remote_op parameter (this indicates the attack surface is exposed)
  5. Audit environment for potential POP chain sources
    List all active plugins and themes on the WordPress installation; research whether any provide PHP magic methods (__wakeup, __destruct, __get, __call) that could be chained with the object injection
    Affected if Additional plugins or themes with exploitable POP chains are present and active alongside vulnerable s2Member Pro

The environment is affected if s2Member Pro version is below 250214, the plugin is active, and the s2member_pro_remote_op parameter is processing untrusted input, especially when other plugins with POP chain capabilities are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 250214 or later
Fixed in 250214
Interim mitigation

Update s2Member Pro to the latest patched version immediately. If no patch is available, disable the plugin and audit the WordPress environment for other plugins/themes that could provide a POP chain.

Recommended fix High confidence

250214

  1. Update the s2Member Pro plugin for WordPress to version 250214 or later via the WordPress plugin dashboard, or replace the plugin files with the version 250214 release.
  2. Verify the update was successful by checking the installed plugin version in the WordPress admin under Plugins > Installed Plugins.
  3. Confirm the 's2member_pro_remote_op' parameter is no longer processing untrusted deserialized data.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in S2member Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12562 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data