UserproWordPress extension · Userproplugin
CVE-2023-6007
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 UserPro plugin for WordPress is vulnerable to unauthorized access of data, modification of data, loss of data due to a missing capability check on multiple functions in all versions up to, and including, 5.1.1. This makes it possible for unauthenticated attackers 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 confidenceThe UserPro WordPress plugin has multiple functions lacking capability checks, allowing unauthenticated attackers to add, modify, or delete user meta fields and plugin options. This broken access control vulnerability enables data tampering and potential privilege escalation without any authentication.
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
<= 5.1.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Verify UserPro plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate the UserPro plugin in the list. Note whether it is active or inactive.Affected if UserPro plugin is installed and active at version 5.1.1 or below
-
Determine installed UserPro versionIn the Plugins list, click on the UserPro plugin to view its details, or check the plugin files for a version constant. Compare the version number against the affected range <= 5.1.1.Affected if Installed version is 5.1.1 or any version lower than 5.1.1
-
Inspect plugin for unauthorized user meta modificationsAccess WordPress database via phpMyAdmin or mysql command. Query the usermeta table for unexpected meta fields added by unknown users, particularly meta keys that may have been created after the plugin was installed. Check wp_usermeta for unfamiliar meta_field entries.Affected if usermeta table contains meta entries created by unauthenticated users or meta fields that were not added through legitimate admin actions
-
Check plugin options for unauthorized changesIn WordPress admin, navigate to UserPro settings or inspect the wp_options table for plugin_option_name entries. Look for any option values that were modified unexpectedly or contain suspicious data.Affected if wp_options table shows plugin options modified by unauthenticated users or contains unexpected configuration changes
-
Review user accounts for privilege escalationIn WordPress admin, go to Users > All Users. Examine user roles and capabilities for any accounts that were added or modified without authorization, especially new administrator-level accounts.Affected if There are unexpected user accounts with elevated roles, particularly administrator accounts created without admin authorization
You are affected if UserPro plugin version 5.1.1 or lower is installed and active, or if unauthorized changes to usermeta, plugin options, or user accounts are detected in the database.
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 UserPro plugin to version 5.1.2 or later which contains the capability check fixes. If an update is unavailable, consider disabling the plugin or implementing firewall rules to restrict access to the vulnerable endpoints.
Fix this in Userpro
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-2023-6007 — 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-2023-6007 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