Vulnerability Database

392,964

Total vulnerabilities in the database

Vulnerabilities for products matching "websphere_portal"

Found 1 matching product.

You can search for specific versions with /product/websphere_portal/1.2.3

ibm / websphere_portal

126 vulnerabilities found
Title Severity Exploit Date Affected versions
Low November 13, 2013 11/13/13
= 7.0.0.0
= 7.0.0.1
= 7.0.0.2
= 8.0.0.0
= 8.0.0.1
Medium August 21, 2013 8/21/13
= 6.1.0.0
= 7.0.0.0
= 7.0.0.0-cf001
= 8.0
= 8.0.0.0
= 8.0.0.0-cf01
= 8.0.0.0-cf02
= 8.0.0.0-cf03
= 8.0.0.0-cf04
= 8.0.0.0-cf05
Medium August 16, 2013 8/16/13
<= 8.0.0.1
= 5.1.0.0
= 5.1.0.1
= 5.1.0.2
= 5.1.0.3
= 5.1.0.4
= 5.1.0.5
= 6.0.0.0
= 6.0.0.1
= 6.0.0.2
= 6.0.0.3
= 6.0.0.4
= 6.0.1.0
= 6.0.1.1
= 6.0.1.2
= 6.0.1.3
= 6.0.1.4
= 6.0.1.5
= 6.0.1.5-wp6015_008_01
= 6.0.1.6
= 6.0.1.7
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
= 6.1.0.3
= 6.1.5.0
= 7.0.0.0
= 7.0.0.0-cf001
= 7.0.0.1
= 7.0.0.1-cf002
= 7.0.0.1-cf003
= 7.0.0.1-cf004
= 7.0.0.1-cf005
= 7.0.0.1-cf006
= 7.0.0.1-cf007
= 7.0.0.1-cf008
= 7.0.0.1-cf009
= 7.0.0.1-cf010
= 7.0.0.1-cf019
= 7.0.0.2
= 7.0.0.2-cf011
= 7.0.0.2-cf012
= 7.0.0.2-cf013
= 7.0.0.2-cf014
= 7.0.0.2-cf015
= 7.0.0.2-cf016
= 7.0.0.2-cf017
= 7.0.0.2-cf018
= 7.0.0.2-cf019
= 7.0.0.2-cf020
= 7.0.0.2-cf021
= 7.0.0.2-cf022
= 8.0
= 8.0.0.0
= 8.0.0.0-cf01
= 8.0.0.0-cf02
= 8.0.0.0-cf03
= 8.0.0.0-cf04
= 8.0.0.0-cf05
= 8.0.0.1
= 8.0.0.1-cf04
= 8.0.0.1-cf05
Medium June 3, 2013 6/3/13
= 7.0.0.0-cf001
= 7.0.0.1
= 7.0.0.1-cf002
= 7.0.0.1-cf003
= 7.0.0.1-cf004
= 7.0.0.1-cf005
= 7.0.0.1-cf006
= 7.0.0.1-cf007
= 7.0.0.1-cf008
= 7.0.0.1-cf009
= 7.0.0.1-cf010
= 7.0.0.1-cf019
= 7.0.0.2
= 7.0.0.2-cf011
= 7.0.0.2-cf012
= 7.0.0.2-cf013
= 7.0.0.2-cf014
= 7.0.0.2-cf015
= 7.0.0.2-cf016
= 7.0.0.2-cf017
= 7.0.0.2-cf018
= 7.0.0.2-cf019
= 7.0.0.2-cf020
= 7.0.0.2-cf021
= 7.0.0.2-cf022
= 8.0
= 8.0.0.0-cf01
= 8.0.0.0-cf02
= 8.0.0.0-cf03
= 8.0.0.0-cf04
= 8.0.0.0-cf05
= 8.0.0.1
= 8.0.0.1-cf04
= 8.0.0.1-cf05
Low June 3, 2013 6/3/13
= 8.0
= 8.0.0.0
= 8.0.0.0-cf01
= 8.0.0.0-cf02
= 8.0.0.0-cf03
= 8.0.0.0-cf04
= 8.0.0.0-cf05
= 8.0.0.1
= 8.0.0.1-cf04
= 8.0.0.1-cf05
= 7.0.0.0
= 7.0.0.0-cf001
= 7.0.0.1
= 7.0.0.1-cf002
= 7.0.0.1-cf003
= 7.0.0.1-cf004
= 7.0.0.1-cf005
= 7.0.0.1-cf006
= 7.0.0.1-cf007
= 7.0.0.1-cf008
= 7.0.0.1-cf009
= 7.0.0.1-cf010
= 7.0.0.1-cf019
= 7.0.0.2
= 7.0.0.2-cf011
= 7.0.0.2-cf012
= 7.0.0.2-cf013
= 7.0.0.2-cf014
= 7.0.0.2-cf015
= 7.0.0.2-cf016
= 7.0.0.2-cf017
= 7.0.0.2-cf018
= 7.0.0.2-cf019
= 7.0.0.2-cf020
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
= 6.1.0.3
= 6.1.5.0
Medium November 30, 2012 11/30/12
= 7.0.0.1
= 7.0.0.1-cf002
= 7.0.0.1-cf003
= 7.0.0.1-cf004
= 7.0.0.1-cf005
= 7.0.0.1-cf006
= 7.0.0.1-cf007
= 7.0.0.1-cf008
= 7.0.0.1-cf009
= 7.0.0.1-cf010
= 7.0.0.1-cf011
= 7.0.0.1-cf012
= 7.0.0.1-cf013
= 7.0.0.1-cf014
= 7.0.0.1-cf015
= 7.0.0.1-cf016
= 7.0.0.1-cf017
= 7.0.0.1-cf018
= 7.0.0.2
= 7.0.0.2-cf002
= 7.0.0.2-cf003
= 7.0.0.2-cf004
= 7.0.0.2-cf005
= 7.0.0.2-cf006
= 7.0.0.2-cf007
= 7.0.0.2-cf008
= 7.0.0.2-cf009
= 7.0.0.2-cf010
= 7.0.0.2-cf011
= 7.0.0.2-cf012
= 7.0.0.2-cf013
= 7.0.0.2-cf014
= 7.0.0.2-cf015
= 7.0.0.2-cf016
= 7.0.0.2-cf017
= 7.0.0.2-cf018
= 8.0.0.0
= 8.0.0.0-cf01
= 8.0.0.0-cf02
Medium July 3, 2012 7/3/12
= 7.0.0.1
= 7.0.0.2
= 8.0
Medium July 17, 2011 7/17/11
= 7.0.0.0
= 7.0.0.1
= 7.0.0.1-cf002
= 7.0.0.1-cf003
= 7.0.0.1-cf004
= 7.0.0.1-cf005
Medium May 26, 2011 5/26/11
= 7.0.0.1
= 7.0.0.1-cf002
= 7.0.0.1-cf003
Medium May 26, 2011 5/26/11
= 6.0.1.7
= 7.0.0.1
Medium January 28, 2011 1/28/11
= 6.0.1.1
= 6.0.1.2
= 6.0.1.3
= 6.0.1.4
= 6.0.1.5
= 6.0.1.6
= 6.0.1.7
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
= 6.1.0.3
= 6.1.5.0
= 7.0.0.0
Medium November 9, 2010 11/9/10
= 6.1.0.1
High April 12, 2010 4/12/10
= 6.0.1.1
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
Medium February 26, 2010 2/26/10
= 5.1.0.0
= 5.1.0.1
= 5.1.0.2
= 5.1.0.3
= 5.1.0.4
= 5.1.0.5
= 6.0.0.0
= 6.0.0.1
= 6.0.0.2
= 6.0.0.3
= 6.0.0.4
= 6.0.1.0
= 6.0.1.1
= 6.0.1.2
= 6.0.1.3
= 6.0.1.4
= 6.0.1.5
= 6.0.1.6
= 6.0.1.7
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
= 6.1.0.3
= 6.1.5.0
Medium February 26, 2010 2/26/10
= 5.1.0.0
= 5.1.0.1
= 5.1.0.2
= 5.1.0.3
= 5.1.0.4
= 5.1.0.5
= 6.0.0.0
= 6.0.0.1
= 6.0.0.2
= 6.0.0.3
= 6.0.0.4
= 6.0.1.0
= 6.0.1.1
= 6.0.1.2
= 6.0.1.3
= 6.0.1.4
= 6.0.1.5
= 6.0.1.6
= 6.0.1.7
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
= 6.1.0.3
= 6.1.5.0
Medium February 25, 2010 2/25/10
= 6.0.1.5-wp6015_008_01
Medium December 2, 2009 12/2/09
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
High December 2, 2009 12/2/09
= 6.1.0.0
= 6.1.0.1
= 6.1.0.2
Medium June 3, 2009 6/3/09
>= 5.1, < 6.0.0.0
Medium April 15, 2009 4/15/09
= 6.0.0.0
= 6.0.1.0
= 6.1.0.0
= 6.1.5.0
= 7.0.0.0
= 8.0.0.0
Medium April 15, 2009 4/15/09
= 6.0.0.0
= 6.0.1.0
= 6.1.0.0
= 6.1.5.0
= 7.0.0.0
= 8.0.0.0
Medium April 15, 2009 4/15/09
= 6.0.0.0
= 6.0.1.0
= 6.1.0.0
= 6.1.5.0
= 7.0.0.0
= 8.0.0.0
High December 19, 2008 12/19/08
<= 6.0.1.4
= 6.0.0.0
= 6.0.0.1
= 6.0.1.1
= 6.0.1.2
= 6.0.1.3
High August 4, 2008 8/4/08
= 5.1.0.0
= 5.1.0.1
= 5.1.0.2
= 5.1.0.3
= 5.1.0.4
= 5.1.0.5
= 6.0.0.0
= 6.0.0.1
= 6.0.1.1
= 6.0.1.3
= 6.1.0.0
Medium June 19, 2007 6/19/07
= 1.0
Medium June 19, 2007 6/19/07
= 1.0

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.