dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-11290

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-07
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 Member Access plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.1.6 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 · high confidence

The Member Access WordPress plugin fails to properly filter restricted content from WordPress core search results. Posts that have been restricted to higher-level roles (such as administrator) are still returned in search results accessible to unauthenticated users, allowing disclosure of sensitive data including post titles, excerpts, and potentially full content metadata.

MitigationUpdate the Member Access plugin to a version beyond 1.1.6 if available, or implement custom search filters to exclude role-restricted posts from unauthenticated queries until a patch is released. Audit exposed content for sensitive information exposure.

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 Member Access plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Member Access' in the list. Alternatively, check the /wp-content/plugins/ directory for a member-access folder.
    Affected if The Member Access plugin is present on the site
  2. Check installed plugin version
    Click 'View details' on the Member Access plugin in the Plugins page, or inspect the main plugin PHP file (usually member-access.php) to find the Version header in the plugin comments.
    Affected if The version is 1.1.6 or lower, or if no version is displayed and the plugin has not been updated recently
  3. Identify role-restricted posts
    Go to Posts > All Posts and look for posts that have restricted access settings applied (check for custom fields, membership restrictions, or use the Member Access settings to view which posts have role-based access controls).
    Affected if There are posts restricted to specific roles (such as administrator or editor) that should not be visible to unauthenticated users
  4. Test unauthenticated search for restricted content
    Open a browser in incognito/private mode (logged out of WordPress), use the site search function to search for keywords from role-restricted posts. Capture the search results and compare against the restricted post titles.
    Affected if Unauthenticated search returns posts that should be restricted to higher-level roles, exposing titles, excerpts, or metadata
  5. Inspect search query results for sensitive metadata
    Examine the returned search results page source or use a debugging tool to inspect if full post content, private notes, or restricted metadata is being exposed in the search results accessible to unauthenticated users.
    Affected if Search results expose excerpts, content snippets, or metadata from posts that should be role-restricted

If the Member Access plugin versions 1.1.6 or below are installed AND role-restricted posts appear in unauthenticated search results, the environment is affected by this CVE.

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 Member Access plugin to a version beyond 1.1.6 if available, or implement custom search filters to exclude role-restricted posts from unauthenticated queries until a patch is released. Audit exposed content for sensitive information exposure.

Recommended fix Moderate confidence

Version 1.1.7 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Member Access plugin
  4. Check if the current version is 1.1.6 or lower
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Verify the update was successful by confirming the new version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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