CVE-2021-24819: The Page/Post Content Shortcode WordPress plugin through 1.0 does not have proper authorisation in place, allo

Q: How do I fix CVE-2021-24819?

page\/post content shortcode: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Q: Is CVE-2021-24819 being exploited?

CVE-2021-24819 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-24819 affect?

CVE-2021-24819 affects page\/post content shortcode. Severity is medium (CVSS 4.3). The Page/Post Content Shortcode WordPress plugin through 1.0 does not have proper authorisation in place, allowing users with a role as low as contributor to access draft/private/password protected/trashed posts/pages they should not be all

Q: How urgent is CVE-2021-24819?

Priority 34/100. Public exploit reference

Routine

MEDIUM 4.3UPGRADE

CVE-2021-24819 is a medium-severity flaw (CVSS 4.3) affecting page\/post content shortcode. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Page/Post Content Shortcode WordPress plugin through 1.0 does not have proper authorisation in place, allowing users with a role as low as contributor to access draft/private/password protected/trashed posts/pages they should not be allowed to, including posts created by other users such as admins and editors.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 43%)
CISA exploited list	No
Weakness	CWE-863
Published	2021-12-13
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: page\/post content shortcode project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-12-13 11:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

page\/post content shortcode project page\/post content shortcode UPGRADE

Affected: <= 1.0

Fixed in: newer than 1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pagepost-content-shortcode || rpm -q pagepost-content-shortcode || pagepost-content-shortcode --version

2. UPGRADE to newer than 1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pagepost-content-shortcode

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pagepost-content-shortcode

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-24819?

page\/post content shortcode: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Is CVE-2021-24819 being exploited?

CVE-2021-24819 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-24819 affect?

CVE-2021-24819 affects page\/post content shortcode. Severity is medium (CVSS 4.3). The Page/Post Content Shortcode WordPress plugin through 1.0 does not have proper authorisation in place, allowing users with a role as low as contributor to access draft/private/password protected/trashed posts/pages they should not be all

How urgent is CVE-2021-24819?

Priority 34/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs