dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-11351

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 Restrict – membership, site, content and user access restrictions for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.2.8 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 Restrict WordPress plugin fails to properly enforce access restrictions when content is queried through WordPress core's built-in search functionality. Unauthenticated attackers can use the search feature to discover and extract sensitive content that has been restricted to higher-privileged roles such as administrators, bypassing the plugin's access control logic.

MitigationUpdate the Restrict plugin to the latest version available. If no patched version exists, consider disabling the plugin's search integration or implementing alternative access control at the web server/application level until a fix is released.

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. Confirm Restrict plugin is installed
    Navigate to WordPress admin > Plugins and locate the Restrict plugin (or 'Restrict Content', 'Restrict User Access', or similar). Verify it is installed and activated.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed version
    In WordPress admin > Plugins, find the Restrict plugin and note the version number displayed. Compare this to any known affected version range if available.
    Affected if The installed version falls within the range containing the vulnerability (pre-fix versions).
  3. Verify WordPress search is enabled and accessible
    Confirm the site's search functionality is active by visiting the site and using the search bar, or by making a GET request to ?s=test. Ensure the search endpoint responds normally.
    Affected if WordPress core search functionality is enabled and publicly accessible.
  4. Test if unrestricted content appears in search results
    Perform a search query as an unauthenticated (logged-out) user using the site's search feature. Search for terms that might appear in content restricted to administrators or other privileged roles (e.g., common post titles, page names). Inspect whether restricted content appears in the search results.
    Affected if Search results return content that should be restricted to users with higher privileges (administrators, editors, etc).

A user is affected if the Restrict plugin is active and unauthenticated search queries can reveal content that should be hidden from non-privileged users.

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 Restrict plugin to the latest version available. If no patched version exists, consider disabling the plugin's search integration or implementing alternative access control at the web server/application level until a fix is released.

Recommended fix Moderate confidence

Version 2.2.9 or later of the Restrict WordPress plugin

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the 'Restrict – membership, site, content and user access restrictions for WordPress' plugin
  4. 4. If an update is available, click 'Update Now' to update to the latest patched version
  5. 5. Verify the update completed successfully by checking the plugin version
  6. 6. Test that the restriction functionality still works correctly by attempting to access restricted content as a low-privileged user

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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