dbcve.org
Ultimate MemberWordPress extension · Ultimatemember

CVE-2018-13136

MEDIUM · 6.1 CVSS v3.0 Published 2018-07-04
Fix available
A fix is available. Upgrade to 2.0.18 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Ultimate Member (aka ultimatemember) plugin before 2.0.18 for WordPress has XSS via the wp-admin settings screen.

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 Ultimate Member WordPress plugin before version 2.0.18 contains a Cross-Site Scripting (XSS) vulnerability in the wp-admin settings screen, allowing attackers to inject malicious scripts through unsanitized user inputs.

MitigationUpdate the Ultimate Member plugin to version 2.0.18 or later to patch the XSS vulnerability in the admin settings screen.

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
Affected:< 2.0.18

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

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Ultimate Member version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > locate Ultimate Member plugin and read the version number from the plugin description
    Affected if The displayed version is below 2.0.18 (for example, 2.0.17, 2.0.16, etc.)
  2. Verify plugin file version header
    Access the plugin file directly via file manager or FTP: open wp-content/plugins/ultimate-member/ultimate-member.php and locate the 'Version:' comment in the file header
    Affected if The version header shows a number less than 2.0.18
  3. Confirm admin settings screen is accessible
    Log in to WordPress admin and navigate to Ultimate Member > Settings in the left sidebar menu
    Affected if You can access the settings screen and the plugin version is below 2.0.18

You are affected if the Ultimate Member plugin version installed is less than 2.0.18 and the wp-admin settings screen is accessible in your environment.

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.

From vendor data
Upgrade available Upgrade to 2.0.18 or later
Fixed in 2.0.18
Interim mitigation

Update the Ultimate Member plugin to version 2.0.18 or later to patch the XSS vulnerability in the admin settings screen.

Fix this in Ultimate Member Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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