dbcve.org
UserproWordPress extension · Userproplugin

CVE-2023-2447

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 5.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 UserPro plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.1.1. This is due to missing or incorrect nonce validation on the 'export_users' function. This makes it possible for unauthenticated attackers to export the users to a csv file, granted they can trick a site administrator into performing an action such as clicking on a link.

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 UserPro WordPress plugin versions up to 5.1.1 lack proper nonce validation on the export_users function, allowing unauthenticated attackers to craft malicious requests that trick administrators into exporting the entire user database to a CSV file via CSRF.

MitigationUpgrade UserPro to version 5.1.2 or later which includes proper nonce validation. If immediate patching is not possible, implement anti-CSRF tokens using wp_verify_nonce() on the export_users function.

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
UserproWordPress extension
Affected:< 5.1.2

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
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 checks

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

  1. Verify UserPro plugin installation and version
    In WordPress admin dashboard, go to Plugins > Installed Plugins and locate UserPro, or check the plugin file header in /wp-content/plugins/userpro/ or via WP-CLI: wp plugin list --name=userpro
    Affected if UserPro version is below 5.1.2 (e.g., 5.1.1, 5.1.0, etc.)
  2. Confirm export_users function exists in the plugin
    Inspect the UserPro plugin files, specifically looking for functions handling user export (commonly in userpro/functions/ or userpro/admin/ directories). Search for 'export_users' or 'export' related functions.
    Affected if The export_users function is present in the plugin code and is accessible to administrators
  3. Check for nonce validation on export function
    Review the PHP code for the export_users function. Look for wp_verify_nonce(), check_admin_referer(), or similar nonce validation calls immediately before any export operation.
    Affected if No nonce validation (wp_verify_nonce, check_admin_referer) is found in the export_users function code
  4. Verify admin CSRF protection status
    Test the export functionality by examining if WordPress nonce tokens are required for the export action, or check if the plugin includes anti-CSRF measures in its admin AJAX handlers or form submissions.
    Affected if The export_users action can be triggered without a valid nonce token, allowing CSRF-based exploitation

You are affected if UserPro plugin version is below 5.1.2 AND the export_users function exists without proper nonce validation, enabling CSRF attacks to trigger unauthorized user data export.

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 5.1.2 or later
Fixed in 5.1.2
Interim mitigation

Upgrade UserPro to version 5.1.2 or later which includes proper nonce validation. If immediate patching is not possible, implement anti-CSRF tokens using wp_verify_nonce() on the export_users function.

Recommended fix High confidence

UserPro version 5.1.2

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the UserPro plugin in the list
  4. 4. If an update is available, click 'Update Now' to update UserPro to version 5.1.2
  5. 5. Alternatively, download UserPro version 5.1.2 from the official source (codecanyon.net)
  6. 6. Deactivate the existing UserPro plugin
  7. 7. Upload and install the new version 5.1.2
  8. 8. Reactivate the plugin

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

Fix this in Userpro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2447 — 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-2023-2447 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