f(x) Private Site <= 1.2.1 - Sensitive Information Exposure

published 2024-03-12 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-16688

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits: 0; none known

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.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 y ago (2024-03-12)

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

turtlepod f(x) Private Site

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Technology feeds

WordPress rss critical rss

References

wordfence.com /threat-intel/vulnerabilities/id/79c3abc6-68fa-4c51-88fa-03ab7d26cc4c?source=cve
third-party-advisory
wordpress.org /plugins/fx-private-site/
product

Sources

CVE List CVE-2024-0906
NVD CVE-2024-0906

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary