# CVE-2024-12447: Information disclosure in Get Post Content Shortcode

> Authenticated contributors can read private, draft, and password-protected post content due to missing validation in the Get Post Content Shortcode plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g6c6-8rrm-qrmr

## What is CVE-2024-12447?

CVE-2024-12447 is a medium-severity vulnerability in webdeveric Get Post Content Shortcode, published on 14 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Get Post Content Shortcode plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 0.4 via the 'post-content' shortcode due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the content of password-protected, private, draft, and pending posts.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2024-12447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12447 is a medium-severity vulnerability in webdeveric Get Post Content Shortcode, published on 14 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12447 in the wild and no public exploit code.

Affected product: webdeveric Get Post Content Shortcode. 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-12447/ (Markdown: https://insights.sbomify.com/CVE-2024-12447/index.md)
```

## Sources

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

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