Users Ultra MembershipWordPress extension · Usersultra
CVE-2015-9402
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.59 for WordPress has uultra-form-cvs-form-conf arbitrary file upload.
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.59 contains an arbitrary file upload vulnerability in the uultra-form-cvs-form-conf component. This allows unauthenticated attackers to upload arbitrary files to the server, potentially including malicious PHP scripts for remote code execution.
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.59CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify the installed version of the users-ultra pluginIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and locate the 'Users Ultra Membership' plugin. The version number is displayed beneath the plugin name.Affected if The displayed version number is lower than 1.5.59 (for example, 1.5.58, 1.5.50, etc.)
-
Verify the vulnerable component is accessibleCheck if the endpoint /wp-admin/admin-ajax.php?action=uultra-form-cvs-form-conf is reachable on the server. This can be tested by attempting a GET request to this URL from an unauthenticated browser or using a tool like curl.Affected if The endpoint responds with any HTTP status code other than 404, indicating the plugin component is active and potentially exploitable
-
Inspect the uploads directory for unexpected filesNavigate to the WordPress uploads folder (typically /wp-content/uploads/) and examine the directory structure. Look for files with extensions that are not standard image, document, or media types, particularly .php, .php5, .phtml, or .exe files.Affected if Any unrecognized PHP scripts or executable files are present in the uploads directory, especially in subdirectories that were not created by legitimate site administrators
-
Review server access logs for suspicious upload requestsExamine web server access logs (Apache error.log, access.log or Nginx access.log) for POST requests to the uultra-form-cvs-form-conf endpoint. Look for patterns where file extensions like .php are being uploaded.Affected if Log entries show POST requests to the vulnerable component containing PHP file extensions or other potentially malicious file types
A defender is affected if the users-ultra plugin version is below 1.5.59 AND the vulnerable component is accessible, or if evidence of unauthorized file uploads exists on the server.
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.59
Update the users-ultra plugin to version 1.5.59 or later. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious file uploads.
Fix this in Users Ultra Membership
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9402 — 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-9402 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