CVE-2015-7397
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 · uneditedMultiple open redirect vulnerabilities in the Aurora starter store in IBM WebSphere Commerce 7.0 through Feature Pack 8 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the referrer parameter.
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 confidenceOpen redirect vulnerability in the Aurora starter store of IBM WebSphere Commerce 7.0 through Feature Pack 8 allows remote attackers to redirect users to arbitrary external websites via the referrer parameter, enabling phishing attacks.
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.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/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.
-
Confirm IBM WebSphere Commerce versionCheck the installed WebSphere Commerce version via the admin console or by inspecting the WC_installdir directory for version information files. The admin console typically displays the version under the runtime information section.Affected if The installed version is IBM WebSphere Commerce 7.0 through Feature Pack 8.
-
Identify if Aurora starter store is in useLog into the WebSphere Commerce Admin console and navigate to the Store Management section. Look for stores configured with the Aurora starter store template. Alternatively, check the store configuration XML files in the WC_eardir/xml directory for Aurora-related store definitions.Affected if An Aurora starter store is deployed and active.
-
Locate redirect handling code using referrer parameterSearch the Aurora store web application files for code that processes the referrer parameter in redirect logic. In the WC_eardir/Stores.war directory, examine servlet and controller files that handle redirection, looking for request.getParameter calls referencing 'referrer' or similar parameters used in redirect URLs.Affected if Code exists that uses the referrer parameter to construct redirect URLs without strict validation.
-
Inspect redirect validation logicReview the redirect handling code identified in the previous step to determine whether proper URL validation is implemented. Check if the code validates that the redirect target belongs to the same domain or is on an allowlist before performing the redirect.Affected if No strict domain validation or allowlist checking is performed on the referrer parameter before redirecting users.
Your environment is affected if you are running IBM WebSphere Commerce 7.0 through Feature Pack 8 with an Aurora starter store that processes the referrer parameter in redirects without proper domain validation.
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 dataImplement strict input validation and allowlist-based URL validation on the referrer parameter to ensure only legitimate, same-domain URLs are permitted for redirection.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7397 — 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-7397 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