CVE-2015-7428
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 · uneditedOpen redirect vulnerability in IBM WebSphere Portal 8.0.x before 8.0.0.1 CF20 and 8.5.x before 8.5.0.0 CF09 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks 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 confidenceIBM WebSphere Portal contains an open redirect vulnerability where the application fails to properly validate redirect URLs, allowing attackers to craft malicious URLs that redirect users to arbitrary external websites. This enables phishing attacks where users believe they are visiting a legitimate IBM WebSphere Portal page but are instead directed to a malicious site.
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= 8.0.0.0= 8.0.0.1= 8.5.0.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.
-
Identify the installed IBM WebSphere Portal versionLocate the version file in the portal installation directory, typically under [PortalServer_root]/doc/VERSION.TXT or check the WebSphere Integrated Solutions Console at Servers > Server Types > WebSphere application servers > [serverName] > Runtime > Version. Alternatively, examine the about.xml file in the portal hierarchy.Affected if The installed version is exactly 8.0.0.0, 8.0.0.1, or 8.5.0.0
-
Verify the portal is accessible via HTTP/HTTPSConfirm the WebSphere Portal web interface is running and reachable by attempting to access the portal URL (e.g., https://[hostname]:[port]/wps/portal). Check that the web container is active.Affected if The portal web interface is enabled and accessible, as the open redirect vulnerability is exploited through crafted URLs to the portal's web endpoints
-
Review URL redirect configuration filesExamine the WebSphere Portal configuration files that handle redirection, particularly redirect.properties or similar files in the [WP_PROFILE]/ConfigEngine directory. Also check the IBM WebSphere Portable Library configuration for any custom redirect handlers.Affected if The system relies on redirect handling logic without explicit URL validation, which is the default behavior in the affected versions
A user is affected if their IBM WebSphere Portal installation is exactly version 8.0.0.0, 8.0.0.1, or 8.5.0.0 and the portal web interface is accessible, since the open redirect vulnerability exists in these specific versions without the corrective fixes applied.
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 Portal corrective fixes: upgrade to version 8.0.0.1 CF20 or later for 8.0.x releases, and upgrade to version 8.5.0.0 CF09 or later for 8.5.x releases.
- 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-7428 — 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-7428 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