Websphere Portal vulnerabilitiesRanked by how likely they are to be used.
Websphere Portal is made by IBM. We track 128 published vulnerabilities listed under that exact name, across 50 versions. None of them is on the list of flaws known to be exploited today. IBM lists newer releases under their own names, such as Websphere Portal Unified Task List Portlet, so check those pages too.
We keep watching the known-exploited list.
Is Websphere Portal listed under other names? Yes.
IBM also lists Websphere Portal under more specific names, such as Websphere Portal Unified Task List Portlet. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Websphere Portal vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Websphere Portal's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Websphere Portal flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 3.8%CVE-2011-0679Medium
IBM WebSphere Portal 6.0.1.1 through 7.0.0.0, as used in IBM Lotus Web Content Management (WCM) and IBM Lotus Quickr for WebSphere Portal, allows remote attackers to obtain sensitive information via a "modified message."
- 3.5%CVE-2010-0714Medium
Cross-site scripting (XSS) vulnerability in login.jsp in IBM WebSphere Portal, IBM Lotus Web Content Management (WCM), and IBM Lotus Workplace Web Content Management 5.1.0.0 through 5.1.0.5, 6.0.0.0 through 6.0.0.4,...
- 3.2%CVE-2015-7419High
IBM WebSphere Portal 8.0.0.1 before CF19 and 8.5.0 before CF09 allows remote attackers to cause a denial of service (memory consumption) via crafted requests.
- 3.0%CVE-2007-3127Medium
content.php in WSPortal 1.0, when magic_quotes_gpc is disabled, allows remote attackers to obtain sensitive information via a "';" (quote semicolon) sequence in the page parameter, which reveals the installation path...
- 2.9%CVE-2017-1577High
IBM WebSphere Portal 7.0, 8.0, 8.5, and 9.0 could allow a remote attacker to traverse directories on the system.
- 2.8%CVE-2012-2181Medium
Directory traversal vulnerability in the Dojo module in IBM WebSphere Portal 7.0.0.1 and 7.0.0.2 before CF14, and 8.0, allows remote attackers to read arbitrary files via a crafted URL.
Running Websphere Portal? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
IBM WebSphere Portal 6.0.1.1 through 7.0.0.0, as used in IBM Lotus Web Content Management (WCM) and IBM Lotus Quickr for WebSphere Portal, allows remote attackers to obtain sensitive information via a "modified message."
- Matched to
- Websphere Portal on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 128 published vulnerabilities listed under the name Websphere Portal, across 50 versions.
None of Websphere Portal's vulnerabilities is on the list of flaws known to be exploited today.
IBM also lists Websphere Portal under more specific names, such as Websphere Portal Unified Task List Portlet. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a EdgeProtect account and track Websphere Portal. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.