Banking Enterprise Collections vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited3 versions
The short answer

Banking Enterprise Collections is made by Oracle. We track 4 published vulnerabilities in it, across 3 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 23 January 2025. If you run Banking Enterprise Collections, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Banking Enterprise Collections flaw added to the known-exploited list is CVE-2020-11023, on 23 January 2025. We keep watching the known-exploited list.

Versions

Which versions of Banking Enterprise Collections do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2020-11023Exploited list, 23 Jan 2025

    JQuery Cross-Site Scripting (XSS) Vulnerability

    2.7.0 to 2.8.0
Known exploited

Which Banking Enterprise Collections vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 6.9
    CVE-2020-11023MediumKnown exploited
    JQuery Cross-Site Scripting (XSS) Vulnerability

    JQuery contains a persistent cross-site scripting (XSS) vulnerability.

    Chance of use85%Known exploited since23 Jan 2025
Exploit likelihood

Which Banking Enterprise Collections 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. 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
  2. 85%
    CVE-2020-11023MediumKnown exploited

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

    CVSS6.9Published29 Apr 2020
  3. 14%

    Vulnerability in the Oracle JDeveloper and ADF product of Oracle Fusion Middleware (component: ADF Faces).

    CVSS9.8Published16 Oct 2019
  4. 1.8%

    Apache Ant 1.1 to 1.9.14 and 1.10.0 to 1.10.7 uses the default temporary directory identified by the Java system property java.io.tmpdir for several tasks and may thus leak sensitive information.

    CVSS6.3Published14 May 2020
Precursor Intelligence

Running Banking Enterprise Collections? 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 4 published vulnerabilities listed under the name Banking Enterprise Collections, across 3 versions. The most recent Banking Enterprise Collections flaw added to the known-exploited list is CVE-2020-11023, on 23 January 2025.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2020-11023.

Each flaw names its own versions, usually as ranges. The newest, CVE-2020-11023, affects 2.7.0 to 2.8.0. The versions for every exploited flaw are listed on this page.

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