dbcve.org
UserplusWordPress extension · Wpuserplus

CVE-2024-9520

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to after 2.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The UserPlus plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to a missing capability check on multiple functions in all versions up to, and including, 2.0. This makes it possible for authenticated attackers with subscriber-level permissions or above, to add, modify, or delete user meta and plugin options.

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 confidence

The UserPlus WordPress plugin up to version 2.0 lacks capability checks on multiple functions, allowing authenticated users with subscriber-level permissions or higher to add, modify, or delete user metadata and plugin options. This is a broken access control vulnerability where the plugin fails to verify that the current user has sufficient privileges before performing sensitive operations.

MitigationUpdate the UserPlus plugin to the latest version when available, or disable and remove the plugin until a patch is released. Review user role assignments and consider implementing additional access controls at the application level as a temporary measure.

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
Affected:<= 2.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify UserPlus plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins. Look for 'UserPlus' or 'Wpuserplus Userplus' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin files in wp-content/plugins/ for a version indicator.
    Affected if The plugin is installed with version 2.0 or lower, or the version cannot be determined (indicating an older release).
  2. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins. Check if UserPlus plugin has an 'Active' status indicator. Also check site functionality that may depend on UserPlus features.
    Affected if The plugin is active and running version 2.0 or lower.
  3. Review existing user roles on the site
    In WordPress admin, go to Users > All Users. Examine the role assigned to each user account. Look for accounts with 'Subscriber' role or any custom roles that grant authenticated user access.
    Affected if Any user account exists with Subscriber role or higher permissions, allowing them to potentially exploit the missing capability checks.
  4. Check plugin capability configuration
    Inspect the UserPlus plugin files (typically in wp-content/plugins/wpuserplus/) for function handlers that process user metadata or plugin options. Look for AJAX handlers or form processing code that lack current_user_can() or capability checks.
    Affected if The plugin code reveals functions handling user metadata or plugin options without proper capability verification before executing sensitive operations.

You are affected if the UserPlus plugin is installed and active at version 2.0 or lower, and any user account with Subscriber-level or higher access exists on the WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.0
Interim mitigation

Update the UserPlus plugin to the latest version when available, or disable and remove the plugin until a patch is released. Review user role assignments and consider implementing additional access controls at the application level as a temporary measure.

Recommended fix Moderate confidence

Latest version after 2.0 (check WordPress plugin repository for 2.1 or later)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the UserPlus plugin
  4. Check if an update is available for the UserPlus plugin
  5. If an update is available, update to the latest version to include the security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Userplus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9520 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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