Websphere Virtual Enterprise vulnerabilitiesRanked by how likely they are to be used.

Product15 versions
The short answer

Websphere Virtual Enterprise is made by IBM. We track 8 published vulnerabilities in it, across 15 versions. None of them is on the list of flaws known to be exploited today. If you run Websphere Virtual Enterprise, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Websphere Virtual Enterprise vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Websphere Virtual Enterprise's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Websphere Virtual Enterprise 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.

50% or more10% to 49%Under 10%
  1. 12%

    IBM WebSphere Application Server Network Deployment 7.0, 8.0, 8.5, and 9.0 could allow a remote attacker to execute arbitrary code on the system with a specially-crafted sequence of serialized objects from untrusted...

    CVSS9.8Published5 Jun 2020
  2. 2.4%

    IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 Network Deployment could allow a remote attacker to obtain sensitive information, caused by sending a specially-crafted URL.

    CVSS5.3Published20 Sep 2019
  3. 2.1%

    IBM WebSphere Application Server 7.x before 7.0.0.39, 8.0.x before 8.0.0.11, and 8.5.x before 8.5.5.7 and WebSphere Virtual Enterprise before 7.0.0.7 allow remote attackers to obtain potentially sensitive information...

    CVSS5.0Published22 Aug 2015
  4. 1.6%

    Cross-site scripting (XSS) vulnerability in the Administration Console in IBM WebSphere Application Server (WAS) 7.x before 7.0.0.33, 8.x before 8.0.0.9, and 8.5.x before 8.5.5.2, and WebSphere Virtual Enterprise 7.x...

    CVSS3.5Published1 May 2014
  5. 1.4%

    Cross-site scripting (XSS) vulnerability in the Administration Console in IBM WebSphere Virtual Enterprise 6.1 before 6.1.1.6 and 7.0 before 7.0.0.4 allows remote authenticated users to inject arbitrary web script or...

    CVSS3.5Published18 Nov 2013
  6. 0.9%

    IBM WebSphere Application Server ND 8.5 and 9.0, and IBM WebSphere Virtual Enterprise 7.0 and 8.0 are vulnerable to cross-site scripting when High Availability Deployment Manager is configured.

    CVSS6.1Published27 Aug 2020
  7. 0.7%

    IBM WebSphere Application Server 8.5 and 9.0 is vulnerable to cross-site scripting.

    CVSS5.4Published6 Mar 2019
  8. 0.4%

    IBM WebSphere Application Server (WAS) 8.5 before 8.5.5.6, and WebSphere Virtual Enterprise 7.0 before 7.0.0.6 for WebSphere Application Server (WAS) 7.0 and 8.0, does not properly implement user roles, which allows...

    CVSS4.4Published14 Jul 2015
Precursor Intelligence

Running Websphere Virtual Enterprise? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Websphere Virtual Enterprise, across 15 versions.

None of Websphere Virtual Enterprise's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Websphere Virtual Enterprise. 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.