CVE-2024-0978: The My Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to

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

my private site: upgrade to 3.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-0978 being exploited?

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

CVE-2024-0978 affects my private site. Severity is medium (CVSS 5.3). The My Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.14 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's site privacy

Q: How urgent is CVE-2024-0978?

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

Routine

MEDIUM 5.3REMOTEUPGRADE

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

The My Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.14 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's site privacy feature and view restricted page and post content.

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.5% (top 60%)
CISA exploited list	No
Weakness	CWE-284
Published	2024-02-29
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: zatzlabs

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

Am I affected?

Timeline

2024-02-29 01:43 UTCPublished CVE record published
2026-06-17 06:54 UTCUpdated Record last modified

zatzlabs my private site UPGRADE

Affected: < 3.1.0

Fixed in: 3.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy my-private-site || rpm -q my-private-site || my-private-site --version

2. UPGRADE to 3.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade my-private-site

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade my-private-site

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-0978?

my private site: upgrade to 3.1.0. Exact commands for each OS are on this page.

Is CVE-2024-0978 being exploited?

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

CVE-2024-0978 affects my private site. Severity is medium (CVSS 5.3). The My Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.14 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's site privacy

How urgent is CVE-2024-0978?

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

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs