CVE-2015-5008
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 · uneditedCross-site scripting (XSS) vulnerability in IBM WebSphere Commerce 6.0 through FP11, 6.0 Feature Pack 4, 7.0 through FP9, 7.0 Feature Pack 5 through 8, and 8.0 before 8.0.0.1 allows remote attackers to inject arbitrary web script or HTML via a crafted URL.
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 confidenceCross-site scripting (XSS) vulnerability in IBM WebSphere Commerce allows remote attackers to inject arbitrary web script or HTML via a crafted URL, potentially enabling session hijacking or unauthorized actions performed as the victim 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= 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.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed WebSphere Commerce versionCheck the version information through the WebSphere Commerce administrative console, or look for version files in the installation directory (such as version.info, about.html, or similar version disclosure files in the product installation path)Affected if The installed version matches any of the following exact versions: 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
-
Verify the web storefront is accessibleConfirm that the IBM WebSphere Commerce web interface (storefront or admin portal) is accessible over HTTP/HTTPS from a browser or using a tool like curlAffected if The web interface is exposed and reachable, as the XSS vulnerability is triggered through crafted URLs to these web endpoints
-
Check for recent security patchesReview installed fix packs or interim fixes through the WebSphere Commerce administrative tools or installation logs to see if FP12 (Fix Pack 12) or later has been appliedAffected if No fix pack has been installed, or the installed fix pack version is earlier than FP12 for WebSphere Commerce v6.0
You are affected if WebSphere Commerce version 6.0.0.0 through 6.0.0.11 is installed and the web interface is accessible without having applied FP12 or later.
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 dataApply the appropriate IBM WebSphere Commerce Fix Pack (FP12 for v6.0, FP10 for v7.0, or upgrade to v8.0.0.1 or later) per IBM's security bulletin. Additionally, implement input validation and output encoding on the affected endpoint as a defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5008 — 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-5008 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