Ultimate MemberWordPress extension · Ultimatemember
CVE-2016-10872
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 ultimate-member plugin before 1.3.40 for WordPress has XSS on the login form.
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 ultimate-member WordPress plugin before version 1.3.40 contains a reflected Cross-Site Scripting (XSS) vulnerability in its login form. An attacker could inject malicious JavaScript code into the login form that executes in the victim's browser when the form is rendered, potentially stealing session cookies or performing actions on behalf of the user.
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
Ultimate MemberWordPress extension
< 1.3.40CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Ultimate Member plugin is installedLocate the ultimate-member plugin directory in your WordPress wp-content/plugins folder, or check the plugin list in WordPress admin under Plugins > Installed Plugins. Look for 'Ultimate Member' in the list.Affected if The plugin is not present in your WordPress installation, so you are not affected.
-
Determine installed plugin versionIn WordPress admin, find 'Ultimate Member' in the Plugins list and note the version number displayed below the plugin name. Alternatively, open the main plugin file (usually ultimate-member/um.php) and look for the 'Version:' header in the file comments.Affected if You are affected if the version number is lower than 1.3.40 (for example, 1.3.39, 1.3.38, etc.).
-
Verify plugin is activeIn WordPress admin under Plugins > Installed Plugins, check if 'Ultimate Member' shows as 'Active' under the plugin status.Affected if If the plugin is installed but not active, the login form XSS vulnerability is not exploitable in your environment.
-
Confirm login form functionality is in useCheck if Ultimate Member login form shortcode [ultimatemember_login] is used on a page, or if Ultimate Member login functionality is enabled in plugin settings under Ultimate Member > Settings > General > Login/Registration. Look for 'Enable Login' or similar option.Affected if You are only affected if the plugin version is below 1.3.40 AND the login form feature is enabled and accessible to users.
You are affected if the Ultimate Member plugin version is below 1.3.40 and the login form feature is enabled and accessible on your site.
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.3.40
Update the ultimate-member plugin to version 1.3.40 or later to patch the XSS vulnerability in the login form.
Fix this in Ultimate Member
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-2016-10872 — 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-2016-10872 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