dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-10937

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-05
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 Related Posts, Inline Related Posts, Contextual Related Posts, Related Content By PickPlugins plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.0.58 via the wp_ajax_nopriv_related_post_ajax_get_post_ids AJAX action. This makes it possible for unauthenticated attackers to extract sensitive data including titles of posts in draft status.

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 PickPlugins Related Posts WordPress plugin has an information disclosure vulnerability in the wp_ajax_nopriv_related_post_ajax_get_post_ids AJAX action. This endpoint is accessible to unauthenticated users and fails to properly restrict access, allowing attackers to retrieve sensitive data including titles of posts in draft status.

MitigationUpdate the plugin to version 2.0.59 or later. If an update is unavailable, consider removing the plugin or implementing firewall rules to block the vulnerable AJAX endpoint until a patch 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. Verify plugin installation
    Navigate to WordPress admin dashboard > Plugins and look for 'PickPlugins Related Posts' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder containing 'related-post' in the name
    Affected if The plugin is installed and active
  2. Identify installed version
    In WordPress admin > Plugins > PickPlugins Related Posts, view the plugin details to find the version number displayed beneath the plugin name
    Affected if Version is lower than 2.0.59 or the version cannot be determined (indicating an unpatched state)
  3. Check AJAX endpoint accessibility
    Send a request to your site via curl or a browser developer tool: /wp-admin/admin-ajax.php?action=related_post_ajax_get_post_ids - inspect whether the endpoint returns a response without requiring authentication
    Affected if The endpoint returns any response (including error messages) without requiring login, indicating the unauthenticated access vector is present

Your environment is affected if the PickPlugins Related Posts plugin is installed, the version is below 2.0.59, and the AJAX endpoint is accessible to unauthenticated 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 plugin to version 2.0.59 or later. If an update is unavailable, consider removing the plugin or implementing firewall rules to block the vulnerable AJAX endpoint until a patch is released.

Recommended fix High confidence

2.0.59 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Related Posts' (or 'Related Posts, Inline Related Posts, Contextual Related Posts, Related Content By PickPlugins') plugin
  4. Click 'Update Now' to install the latest version

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

Have this fixed 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 help mitigating

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-10937 — 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-10937 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