CVE-2024-0906: The f(x) Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up

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

f\(x\) private site: upgrade to newer than 1.2.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-0906 being exploited?

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

CVE-2024-0906 affects f\(x\) private site. Severity is medium (CVSS 5.3). The f(x) Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2.1 via the API. This makes it possible for unauthenticated attackers to obtain page and post contents of a s

Q: How urgent is CVE-2024-0906?

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

Routine

MEDIUM 5.3REMOTEUPGRADE

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

The f(x) Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2.1 via the API. This makes it possible for unauthenticated attackers to obtain page and post contents of a site protected with this plugin.

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-200
Published	2024-03-12
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: shellcreeper

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

Am I affected?

Timeline

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

shellcreeper f\(x\) private site UPGRADE

Affected: <= 1.2.1

Fixed in: newer than 1.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

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

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fx-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-0906?

f\(x\) private site: upgrade to newer than 1.2.1. Exact commands for each OS are on this page.

Is CVE-2024-0906 being exploited?

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

CVE-2024-0906 affects f\(x\) private site. Severity is medium (CVSS 5.3). The f(x) Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2.1 via the API. This makes it possible for unauthenticated attackers to obtain page and post contents of a s

How urgent is CVE-2024-0906?

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

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs