Banking Digital Experience vulnerabilitiesRanked by how likely they are to be used.

Product8 versions
The short answer

Banking Digital Experience is made by Oracle. We track 31 published vulnerabilities in it, across 8 versions. None of them is on the list of flaws known to be exploited today. If you run Banking Digital Experience, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Banking Digital Experience vulnerabilities are being exploited?

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

None of Banking Digital Experience's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Banking Digital Experience 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. >99%

    In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e.

    CVSS6.1Published29 Apr 2020
  2. 87%

    jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution.

    CVSS6.1Published20 Apr 2019
  3. 82%

    In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory.

    CVSS5.3Published1 Apr 2021
  4. 19%

    FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPConfig (aka anteros-core).

    CVSS9.8Published2 Mar 2020
  5. 13%

    Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel.

    CVSS8.2Published24 Feb 2021
  6. 13%

    When reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.

    CVSS7.5Published13 Jul 2021
  7. 12%

    When reading a specially crafted 7Z archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.

    CVSS7.5Published13 Jul 2021
  8. 12%

    When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop.

    CVSS7.5Published13 Jul 2021
  9. 11%

    When reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.

    CVSS7.5Published13 Jul 2021
  10. 11%

    In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to...

    CVSS4.8Published13 Apr 2021
Precursor Intelligence

Running Banking Digital Experience? 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 31 published vulnerabilities listed under the name Banking Digital Experience, across 8 versions.

None of Banking Digital Experience's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Banking Digital Experience. 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.