dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-8326

HIGH · 8.8 CVSS v3.1 Published 2024-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 241114 via the 'sc_get_details' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including user data and database configuration information, which can lead to reading, updating, or dropping database tables. The vulnerability was partially patched in version 241114.

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 WordPress plugin has a broken access control vulnerability in the 'sc_get_details' function that allows authenticated users with Contributor-level permissions to access sensitive administrative functions and data. This exposes user PII and database configuration details, enabling attackers to potentially read, modify, or delete database tables.

MitigationUpdate the s2Member plugin to the latest version beyond 241114 and verify the partial patch is complete. Review access controls and audit logs for any exploitation attempts.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin is installed
    Check your WordPress installation for the s2Member plugin in wp-content/plugins/ directory or via WordPress admin under Plugins
    Affected if s2Member plugin files are present in the plugins directory and active
  2. Identify the installed s2Member version
    Read the plugin version from the main s2Member PHP file header, readme.txt file, or view the version in WordPress admin under Plugins > Installed Plugins
    Affected if The version number is 241114 or earlier (all versions up to and including 241114 are affected)
  3. Check for users with Contributor-level access or higher
    Review user accounts in WordPress admin under Users, or query the wp_usermeta table, to identify accounts assigned the Contributor role or higher privileges
    Affected if Any user account exists with Contributor, Author, Editor, or Administrator role
  4. Verify the sc_get_details function is present
    Search the s2Member plugin files for the 'sc_get_details' function definition, typically in the main plugin file or includes directory
    Affected if The sc_get_details function exists in the installed plugin code

You are affected if s2Member plugin version 241114 or earlier is installed and active on your WordPress site AND your site has at least one user with Contributor-level access or higher, which would allow exploitation of the sc_get_details function to expose sensitive data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the s2Member plugin to the latest version beyond 241114 and verify the partial patch is complete. Review access controls and audit logs for any exploitation attempts.

Recommended fix Moderate confidence

Upgrade to the latest version of s2Member (version 241206 or later, if available) to obtain the complete fix

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to your WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate the s2Member plugin.
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. After updating, verify the version number matches or exceeds the fully patched release.
  7. 7. Test that the 'sc_get_details' function no longer exposes sensitive information.
  8. 8. Ensure users with Contributor-level access cannot access sensitive data or database configuration.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8326 — 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-8326 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