UserplusWordPress extension · Wpuserplus
CVE-2024-9519
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 UserPlus plugin for WordPress is vulnerable to unauthorized modification of data due to an improper capability check on the 'save_metabox_form' function in versions up to, and including, 2.0. This makes it possible for authenticated attackers, with editor-level permissions or above, to update the registration form role to administrator, which leads to privilege escalation.
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 UserPlus WordPress plugin (versions up to 2.0) lacks proper capability verification on the 'save_metabox_form' function, allowing authenticated users with editor-level permissions to modify the plugin's registration form settings. This IDOR-style flaw enables privilege escalation by allowing attackers to change the default registration role to administrator.
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
UserplusWordPress extension
<= 2.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 UserPlus plugin is installedNavigate to WordPress admin panel, go to Plugins > Installed Plugins, and look for 'UserPlus' or 'Wpuserplus Userplus' in the list of active plugins.Affected if UserPlus plugin appears in the installed plugins list.
-
Check installed UserPlus versionIn the plugins list, click on the plugin name or view the plugin details to find the version number. Compare this version to the affected range (2.0 and below).Affected if The installed version is 2.0 or lower.
-
Locate the plugin filesAccess the WordPress site via FTP or file manager and navigate to /wp-content/plugins/ and look for a directory named 'userplus', 'wpuserplus', or similar.Affected if A UserPlus plugin directory exists in the plugins folder.
-
Inspect the save_metabox_form functionOpen the main plugin PHP file and search for the function named 'save_metabox_form'. Verify if it contains a capability check (such as 'current_user_can' or 'manage_options') before processing the form data.Affected if The function exists but lacks a proper capability check (e.g., does not verify 'manage_options' or equivalent high-level permission before saving settings).
-
Test registration role setting accessibilityLog in with a user who has editor-level permissions. Navigate to the UserPlus registration form settings (typically under UserPlus menu in admin). Attempt to change the default registration role to Administrator.Affected if An editor-level user can successfully change the default registration role to Administrator without receiving an access denied error.
A WordPress site is affected if the UserPlus plugin is installed with version 2.0 or lower and the save_metabox_form function lacks proper capability verification, allowing editors to escalate privileges.
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 UserPlus to version 2.1 or later which implements proper capability checks on the save_metabox_form function. If no update is available, remove the plugin until a patched version is released.
Fix this in Userplus
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9519 — 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-9519 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