CVE-2024-0680: The WP Private Content Plus plugin for WordPress is vulnerable to information disclosure in all versions up to

Q: How do I fix CVE-2024-0680?

wp private content plus: upgrade to 3.6.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-0680 being exploited?

CVE-2024-0680 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-2024-0680 affect?

CVE-2024-0680 affects wp private content plus. Severity is medium (CVSS 5.3). The WP Private Content Plus plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 3.6. This is due to the plugin not properly restricting access to posts via the REST API when a page has been mad

Q: How urgent is CVE-2024-0680?

Priority 36/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2024-0680 is a medium-severity flaw (CVSS 5.3) affecting wp private content plus. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Private Content Plus plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 3.6. This is due to the plugin not properly restricting access to posts via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected posts.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-693
Published	2024-02-28
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wpexpertdeveloper

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

Am I affected?

Timeline

2024-02-28 09:15 UTCPublished CVE record published
2026-06-17 06:54 UTCUpdated Record last modified

wpexpertdeveloper wp private content plus UPGRADE

Affected: < 3.6.1

Fixed in: 3.6.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-private-content-plus || rpm -q wp-private-content-plus || wp-private-content-plus --version

2. UPGRADE to 3.6.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-private-content-plus

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-private-content-plus

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-2024-0680?

wp private content plus: upgrade to 3.6.1. Exact commands for each OS are on this page.

Is CVE-2024-0680 being exploited?

CVE-2024-0680 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-2024-0680 affect?

CVE-2024-0680 affects wp private content plus. Severity is medium (CVSS 5.3). The WP Private Content Plus plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 3.6. This is due to the plugin not properly restricting access to posts via the REST API when a page has been mad

How urgent is CVE-2024-0680?

Priority 36/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2021-4385 MEDIUM 4.3 UPGRADE The WP Private Content Plus plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to

References

← Back to latest CVEs