WordPress security changelog
MEDIUM CVE-2024-0906 Modified

f(x) Private Site: Sensitive information exposure

f(x) Private Site is affected by sensitive information exposure. The vulnerable path is reachable without authentication. Successful exploitation can disclose data that should not be available to the caller.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
f(x) Private Site
Plugin slug
fx-private-site
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Mar 12, 2024
Weakness
CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor
NVD-CWE-noinfo

This CVE was published Mar 12, 2024 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update f(x) Private Site to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Primary and upstream sources