Wp MembersWordPress extension · Butlerblog
CVE-2024-1852
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 WP-Members Membership Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the X-Forwarded-For header in all versions up to, and including, 3.4.9.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page which is the edit users page. This vulnerability was partially patched in version 3.4.9.2, and was fully patched in 3.4.9.3.
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 WP-Members Membership Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the X-Forwarded-For HTTP header due to insufficient input sanitization and output escaping. Unauthenticated attackers can inject arbitrary JavaScript that executes when users access the plugin's edit users page. The vulnerability affects all versions up to 3.4.9.2, with partial mitigation in 3.4.9.2 and full patch in 3.4.9.3.
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
Wp MembersWordPress extension
< 3.4.9.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm WP-Members plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'WP-Members Membership Plugin' in the installed plugins list, or check for the plugin files in /wp-content/plugins/Affected if The plugin is listed as installed and active
-
Check installed plugin versionIn WordPress admin, go to Plugins > WP-Members Membership Plugin and view the version number displayed, or read the version from the plugin header comment in the main plugin PHP fileAffected if The version is less than 3.4.9.3 (versions 3.4.9.2 and below are vulnerable, 3.4.9.2 has partial mitigation)
-
Verify X-Forwarded-For header processingCheck if the site is behind a proxy or load balancer that would cause the web server or application to process X-Forwarded-For headers. Review server configuration (nginx/apache) or any proxy settings that handle this header.Affected if X-Forwarded-For headers are being processed by the application (this is the attack vector for the vulnerability)
-
Confirm user access to edit users pageNavigate to Users > All Users in the WordPress admin panel and verify if the Edit User functionality is accessible to user roles that can access the plugin's user management featuresAffected if Users with access to the plugin's edit users page exist in the system (the malicious script executes when this page is accessed)
You are affected if the WP-Members plugin is installed with a version below 3.4.9.3, your server processes X-Forwarded-For headers, and users who can access the edit users page exist in your WordPress site.
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.
dbcve · scoped3.4.9.3
Update the WP-Members Membership Plugin to version 3.4.9.3 or later to remediate this vulnerability.
3.4.9.3
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find the WP-Members plugin
- Check if current version is below 3.4.9.3
- If vulnerable, click Update Now to upgrade to version 3.4.9.3 or later
- Alternatively, download the latest version from wordpress.org/plugins/wp-members and upload via Plugins > Add New > Upload Plugin
- After updating, verify the version number reflects 3.4.9.3 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Members
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1852 — 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-1852 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