# CVE-2024-10937: Information disclosure in Related Posts By PickPlugins

> Unauthenticated attackers can extract sensitive data, including titles of draft posts, via an AJAX action in the Related Posts plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q7mc-mg4x-393f

## What is CVE-2024-10937?

CVE-2024-10937 is a medium-severity vulnerability in Related Posts By PickPlugins, published on 5 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-10937?


## How do I fix CVE-2024-10937?

No fix has been published for CVE-2024-10937 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10937 being exploited?

There is no known exploitation of CVE-2024-10937 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10937 and fix it if it is affected.

What it is: CVE-2024-10937 is a medium-severity vulnerability in Related Posts By PickPlugins, published on 5 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10937 in the wild and no public exploit code.

Affected product: Related Posts By PickPlugins. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10937/ (Markdown: https://insights.sbomify.com/CVE-2024-10937/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10937
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10937
- OSV: https://osv.dev/vulnerability/CVE-2024-10937

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10937/
Summaries are generated and may contain mistakes; the official description above is the record.