Engineering Lifecycle Optimization - Publishing vulnerabilitiesRanked by how likely they are to be used.

Product15 versions
The short answer

Engineering Lifecycle Optimization - Publishing is made by IBM. We track 28 published vulnerabilities in it, across 15 versions. None of them is on the list of flaws known to be exploited today. If you run Engineering Lifecycle Optimization - Publishing, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Engineering Lifecycle Optimization - Publishing vulnerabilities are being exploited?

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

None of Engineering Lifecycle Optimization - Publishing's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Engineering Lifecycle Optimization - Publishing 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. 2.6%

    IBM Jazz Foundation and IBM Engineering products could allow a remote attacker to bypass security restrictions, caused by improper access control.

    CVSS8.8Published2 Jun 2021
  2. 1.3%

    Unrestricted file upload vulnerability in the Document Builder in IBM Rational Publishing Engine (aka RPENG) 2.0.1 before ifix002 allows remote authenticated users to execute arbitrary code by specifying an...

    CVSS5.4Published8 Aug 2016
  3. 1.2%

    IBM Jazz Foundation and IBM Engineering products could allow a remote attacker to obtain sensitive information when an error message is returned in the browser.

    CVSS6.5Published2 Jun 2021
  4. 1.2%

    IBM Publishing Engine 6.0.6, 6.0.6.1, and 7.0 does not set the secure attribute on authorization tokens or session cookies.

    CVSS4.7Published16 Jul 2020
  5. 1.0%

    IBM Publishing Engine 2.1.2, 6.0.5, and 6.0.6 is vulnerable to cross-site scripting.

    CVSS5.4Published4 Jan 2019
  6. 1.0%

    IBM Publishing Engine 2.1.2, 6.0.5, and 6.0.6 is vulnerable to cross-site scripting.

    CVSS5.4Published4 Jan 2019
  7. 0.8%

    IBM Jazz Foundation and IBM Engineering products could allow an authenticated user to obtain sensitive information due to lack of security restrictions.

    CVSS6.5Published2 Jun 2021
  8. 0.8%

    IBM Engineering Lifecycle Optimization - Publishing 6.0.6, 6.0.6.1, 7.0, 7.0.1, and 7.0.2 could allow a remote attacker to upload arbitrary files, caused by improper access controls.

    CVSS6.5Published14 Jul 2022
  9. 0.7%

    IBM Engineering Lifecycle Optimization - Publishing 6.0.6, 6.0.6.1, 7.0, 7.0.1, and 7.0.2 could disclose highly sensitive information through an HTTP GET request to an authenticated user.

    CVSS6.5Published14 Jul 2022
  10. 0.7%

    IBM Rational Publishing Engine 6.0.5 and 6.0.6 is vulnerable to cross-site scripting.

    CVSS5.4Published12 Oct 2018
EdgeProtect

Running Engineering Lifecycle Optimization - Publishing? 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 28 published vulnerabilities listed under the name Engineering Lifecycle Optimization - Publishing, across 15 versions.

None of Engineering Lifecycle Optimization - Publishing's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Engineering Lifecycle Optimization - Publishing. 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.