CVE-2015-5015
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 · uneditedIBM WebSphere Commerce Enterprise 7.0.0.9 and 8.x before Feature Pack 8 allows remote attackers to obtain sensitive information via a crafted REST 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 confidenceIBM WebSphere Commerce Enterprise versions 7.0.0.9 and 8.x before Feature Pack 8 contains a vulnerability where crafted REST URLs can be used by remote attackers to bypass intended access restrictions and obtain sensitive information. The vulnerability resides in the REST endpoint handling mechanism.
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<= 7.0.0.9CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 installed WebSphere Commerce versionCheck the version using the WebSphere Commerce tool 'versionInfo' or look in the WC_installation_directory/version directory for version details. Look for files like version.txt or in the Installation Manager registry.Affected if The installed version is 7.0.0.9 or earlier, or is 8.x before Feature Pack 8
-
Confirm REST endpoint is enabledInspect the WebSphere Commerce configuration files (REST-config.xml or wc-server.xml in the xml/config directory) to verify the REST endpoint servlet mapping is active. Check the IBM WebSphere Application Server administration console for the REST servlet (RESTEndpointServlet) in the deployed applications.Affected if The REST endpoint servlet is deployed and enabled in the WebSphere Commerce application
-
Test REST endpoint access without credentialsUsing a web browser or curl command, attempt to access a typical REST URL pattern such as: http://hostname/webapp/wcs/stores/servlet/StoreCatalogDisplay?storeId=... or similar REST resource endpoints. Observe whether data is returned without authentication prompts.Affected if The REST endpoint returns sensitive catalog, customer, or order data without requiring authentication
You are affected if your IBM WebSphere Commerce Enterprise version is 7.0.0.9 or earlier, or 8.x before Feature Pack 8, and the REST endpoint is enabled and accessible without authentication.
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 dataUpgrade IBM WebSphere Commerce to Feature Pack 8 or later. If immediate patching is not possible, review and restrict REST API access patterns, implement web application firewall rules to detect and block suspicious URL patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5015 — 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-5015 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