Users Ultra MembershipWordPress extension · Usersultra
CVE-2015-9393
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 users-ultra plugin before 1.5.63 for WordPress has XSS via the p_desc parameter.
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 users-ultra WordPress plugin before version 1.5.63 contains a stored Cross-Site Scripting (XSS) vulnerability in the p_desc parameter, allowing authenticated attackers to inject malicious JavaScript into user profile descriptions that will execute when other users view the affected profiles.
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
Users Ultra MembershipWordPress extension
< 1.5.63CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if users-ultra plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect /wp-content/plugins/ directory for users-ultra folderAffected if The users-ultra plugin folder exists in the WordPress plugins directory
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Users Ultra, or open the main plugin PHP file and look for version comment/constantAffected if The version number displayed is lower than 1.5.63 (e.g., 1.5.60, 1.5.62, etc.)
-
Verify authenticated user access existsCheck if any WordPress user role (subscriber, contributor, author, editor) exists in the system, as the vulnerability requires authenticated access to modify profile descriptionsAffected if User accounts exist with permission to edit their profile descriptions in the users-ultra plugin
-
Inspect user profile descriptions for injected scriptsQuery the database table for user profile meta (typically wp_usermeta with meta_key like 'p_desc' or 'description'), or view user profiles on the frontend to check for unsanitized contentAffected if User profile descriptions contain unescaped HTML script tags or JavaScript event handlers (e.g., <script>, onerror=, onload=, javascript:)
The environment is affected if the users-ultra plugin version is below 1.5.63 AND any user profile description field contains unescaped HTML/JavaScript that could execute in another user's browser.
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 data1.5.63
Update the users-ultra plugin to version 1.5.63 or later to include proper input sanitization, or implement output escaping for the p_desc parameter in the plugin code.
Fix this in Users Ultra Membership
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9393 — 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-2015-9393 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