Get Post Content Shortcode <= 0.4 — Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Disclosure via post_content Shortcode

Am I affected?

• Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Get Post Content Shortcode.
• No admin access? Run a passive check of your site. It reads public files only.

What to do

1. No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
3. Watch Get Post Content Shortcode to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Francesco Carlucci.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

• Advisorywordfence.com

Timeline

1. Dec 13, 2024

   CVE published

   Severity medium, CVSS 4.3

2. Nov 13, 2026

   Record last updated