dbcve.org
UserproWordPress extension · Userproplugin

CVE-2023-2439

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to 5.1.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Stored Cross-Site Scripting via the 'userpro' shortcode in versions up to, and including, 5.1.5 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 before version 5.1.6 contains a stored XSS vulnerability in the 'userpro' shortcode handler. Authenticated contributors+ can inject arbitrary JavaScript via unsanitized shortcode attributes that are reflected without proper escaping when pages are rendered.

MitigationUpdate UserPro to version 5.1.6 or later. Until then, restrict contributor-level permissions and audit pages using the userpro shortcode for malicious content.

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.6

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm UserPro plugin is installed
    Navigate to WordPress admin > Plugins and look for 'UserPro' in the installed plugins list, or check the file system at wp-content/plugins/userpro/ for the plugin directory
    Affected if UserPro plugin is present on the WordPress site
  2. Identify installed UserPro version
    In WordPress admin > Plugins, click on the UserPro plugin to view its details and version number, or open and read the main plugin file header at wp-content/plugins/userpro/userpro.php for the Version field
    Affected if The version shown is less than 5.1.6 (for example, 5.1.5, 5.1.0, or any version below 5.1.6)
  3. Detect userpro shortcode usage in content
    Search the WordPress database or use a plugin to find all posts, pages, and custom post types containing the shortcode [userpro] by querying the wp_posts table for this string, or use a search tool across exported content files
    Affected if The userpro shortcode appears in any published content on the site
  4. Verify contributor-level user accounts exist
    In WordPress admin > Users, review the user list to identify any accounts assigned the 'Contributor' role or higher (Author, Editor, Administrator) who could potentially use the shortcode
    Affected if There are users with Contributor or higher roles who have access to create or edit content containing the shortcode

You are affected if UserPro version is below 5.1.6 AND the userpro shortcode is in use on your site with contributor-level or higher users having access to create or edit content.

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.6 or later
Fixed in 5.1.6
Interim mitigation

Update UserPro to version 5.1.6 or later. Until then, restrict contributor-level permissions and audit pages using the userpro shortcode for malicious content.

Recommended fix High confidence

UserPro version 5.1.6

  1. 1. Create a complete backup of your WordPress site (database and files)
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the UserPro plugin in the list
  4. 4. Click 'Update now' if an update is available, or manually upload version 5.1.6 from the WordPress repository/vendor
  5. 5. After updating, verify the plugin shows version 5.1.6
  6. 6. Test the userpro shortcode functionality to ensure it works correctly
  7. 7. Clear any caching plugins if present

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

Fix this in Userpro Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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