dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-11008

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Members – Membership & User Role Editor Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.2.10 via the WordPress core search feature. This makes it possible for unauthenticated attackers to extract sensitive data from posts that have been restricted to higher-level roles such as administrator.

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 · moderate confidence

The Members WordPress plugin fails to properly restrict content access via the WordPress core search feature, allowing unauthenticated attackers to bypass role-based access controls and extract sensitive data from posts that should be restricted to higher-privileged roles like administrator.

MitigationUpdate the Members plugin to a patched version beyond 3.2.10 and audit all restricted content to confirm the vulnerability has been mitigated and sensitive data is no longer exposed through search results.

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

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

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 Members plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Members' in the list. Alternatively, check the /wp-content/plugins/members/ directory exists on the server.
    Affected if The Members plugin is installed and active on the WordPress site
  2. Check installed Members plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Members plugin. The version number is displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/members/members.php for the Version comment.
    Affected if The installed version is 3.2.10 or lower (any version up to and including 3.2.10)
  3. Identify restricted content configured in Members
    In WordPress admin, go to Members > Roles to review created roles and their capabilities. Check Posts > All Posts to identify posts with non-public visibility or restricted access settings.
    Affected if The site uses Members plugin to restrict content to specific roles beyond Subscriber
  4. Test WordPress core search for restricted content
    Perform a search query on the WordPress site using a specific keyword likely to appear in restricted posts (without being logged in or while logged in as a low-privilege user like Subscriber). Visit the search results page and examine whether restricted posts appear in results.
    Affected if Posts restricted to administrator or other privileged roles appear in search results accessible to unauthenticated or low-privilege users

A site is affected if the Members plugin version is 3.2.10 or lower AND restricted content is accessible through WordPress core search to users who should not have access based on role settings.

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 Members plugin to a patched version beyond 3.2.10 and audit all restricted content to confirm the vulnerability has been mitigated and sensitive data is no longer exposed through search results.

Recommended fix Moderate confidence

Version 3.2.11 or later (latest available version from WordPress plugin repository)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Members – Membership & User Role Editor' plugin
  4. Check the current installed version (should be 3.2.10 or below if vulnerable)
  5. Update the plugin to the latest available version from the WordPress plugin repository
  6. Verify the update completed successfully
  7. Test that restricted content is no longer accessible via WordPress core search by unauthenticated users
Caveat Minor - review plugin settings after upgrade to ensure role permissions are configured as expected

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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