dbcve.org
Websphere CommerceApplication · Ibm

CVE-2015-5007

HIGH · 8.8 CVSS v3.0 Published 2016-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-site request forgery (CSRF) vulnerability in IBM WebSphere Commerce 6.0 through 6.0.0.11, 7.0 through 7.0.0.9, and 7.0 Feature Pack 8 allows remote authenticated users to hijack the authentication of arbitrary users for requests that insert XSS sequences.

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

CSRF vulnerability in IBM WebSphere Commerce allows authenticated attackers to craft malicious requests that, when triggered by authenticated users, inject XSS sequences while hijacking the victim's session authentication.

MitigationApply IBM WebSphere Commerce security patches for versions 6.0.0.11 and below, 7.0.0.9 and below, and Feature Pack 8. Additionally, implement anti-CSRF tokens and validate input/output encoding to prevent XSS injection.

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
Websphere CommerceApplication
Affected:= 6.0.0.0= 6.0.0.1= 6.0.0.2= 6.0.0.3= 6.0.0.4= 6.0.0.5= 6.0.0.6= 6.0.0.7= 6.0.0.8= 6.0.0.9= 6.0.0.10= 6.0.0.11

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

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

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

  1. Identify the installed WebSphere Commerce version
    Run the version check command for your installation, typically found in the Commerce toolkit or by inspecting the WC/toolkit/version folder, or check the Installation Manager inventory file. Common paths include: WC_installdir/version or look at the product.xml in the installation directory.
    Affected if The installed version is any of: 6.0.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5, 6.0.0.6, 6.0.0.7, 6.0.0.8, 6.0.0.9, 6.0.0.10, or 6.0.0.11
  2. Confirm session-based authentication is in use
    Review the WebSphere Commerce configuration files (such as WC.xml or struts-config.xml) to determine if user sessions are managed through the standard session mechanism, or inspect HTTP traffic during login to verify session cookie handling.
    Affected if The application uses standard session authentication where a session cookie is issued upon login and subsequent requests rely on that session token.
  3. Inspect for anti-CSRF token implementation
    Examine the web application forms and AJAX requests for the presence of anti-CSRF tokens. Check if forms include a hidden token field that is validated server-side, or review the application configuration for CSRF protection settings.
    Affected if Anti-CSRF tokens are NOT implemented or are not being validated server-side on form submissions and state-changing requests.
  4. Check input validation and output encoding settings
    Review the WebSphere Commerce deployment descriptor (web.xml) and any custom servlet filters for input validation logic. Inspect JSP files and controller commands for output encoding mechanisms such as usage of escape functions or the WebSphere Commerce Encoder utility.
    Affected if Input validation is missing or weak, and output encoding is not consistently applied to prevent XSS injection.

You are affected if your IBM WebSphere Commerce version is 6.0.0.0 through 6.0.0.11 and the application relies on session authentication without proper anti-CSRF token protection and input/output encoding safeguards.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM WebSphere Commerce security patches for versions 6.0.0.11 and below, 7.0.0.9 and below, and Feature Pack 8. Additionally, implement anti-CSRF tokens and validate input/output encoding to prevent XSS injection.

Fix this in Websphere Commerce Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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