F\(x\) Private SiteWordPress extension · Shellcreeper
CVE-2024-0906
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe f(x) Private Site WordPress plugin up to version 1.2.1 has an API endpoint that incorrectly exposes the content of protected pages and posts to unauthenticated users, effectively bypassing the access restrictions the plugin is designed to enforce.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
F\(x\) Private SiteWordPress extension
<= 1.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if f(x) Private Site plugin is installedCheck WordPress plugins directory or wp-content/plugins for 'fx-private-site' or 'fx-private-site' folder, or view installed plugins via WordPress admin dashboardAffected if The plugin folder exists in the WordPress installation
-
Check the installed version of the pluginLook for version information in the plugin's main PHP file header (usually in wp-content/plugins/fx-private-site/fx-private-site.php) under 'Version:' field, or check via WordPress admin plugin listAffected if Version is 1.2.1 or lower
-
Verify if the API endpoint is accessibleSend a GET request to the site's REST API endpoint (typically /wp-json/fx-private-site/v1/protected-content or similar) without authentication headers to test if protected content is returnedAffected if Unauthenticated requests return content from pages/posts that should be private
-
Check WordPress access control configurationReview the plugin settings in WordPress admin under the plugin's settings page to confirm private content restrictions are enabled, then test accessing a protected page as a logged-out userAffected if Protected content is visible to unauthenticated users despite settings showing restrictions are enabled
You are affected if f(x) Private Site plugin version 1.2.1 or lower is installed and the API endpoint exposes protected content to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the f(x) Private Site plugin to the latest version beyond 1.2.1. If no patched version is available, consider alternative access control solutions or temporarily disable the plugin while implementing server-level access restrictions.
Fix this in F\(x\) Private Site
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0906 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0906 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data