dbcve.org
Websphere CommerceApplication · Ibm

CVE-2016-6090

CRITICAL · 9.8 CVSS v3.1 Published 2017-02-01
Fix available
A fix is available. Upgrade to after 8.0.1.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
IBM WebSphere Commerce contains an unspecified vulnerability that could allow disclosure of user personal data, performing of unauthorized administrative operations, and potentially causing a denial of service.

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

A detailed technical summary for this CVE is being prepared.

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
Websphere CommerceApplication
Affected:>= 6.0.0.0, <= 6.0.0.11>= 7.0.0.0, <= 7.0.0.9>= 8.0.0.0, <= 8.0.0.16>= 8.0.1.0, <= 8.0.1.8= 8.0.3.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.1.8
Vendor patch www.ibm.com →
Recommended fix High confidence

Upgrade to the latest supported WebSphere Commerce version (V6.0.0.12+, V7.0.0.10+, V8.0.0.17+, or V8.0.1.9+); preferably migrate to current supported release

  1. 1. Review IBM Security Bulletin swg21992759 for detailed patch information
  2. 2. Identify your current WebSphere Commerce version using the version command or administration console
  3. 3. For V6.0.0.x: Upgrade to WebSphere Commerce V6.0.0.12 or later (or migrate to a supported newer version)
  4. 4. For V7.0.0.x: Upgrade to WebSphere Commerce V7.0.0.10 or later
  5. 5. For V8.0.0.x: Upgrade to WebSphere Commerce V8.0.0.17 or later
  6. 6. For V8.0.1.x: Upgrade to WebSphere Commerce V8.0.1.9 or later
  7. 7. After upgrade, verify the fix by checking the IBM fix list and testing the Commerce functionality
  8. 8. Ensure backup of current configuration and data before performing upgrade
Caveat Major version upgrades may require code changes, compatibility testing, and data migration; review IBM migration guides

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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