Communications Element Manager vulnerabilitiesAnd the versions its exploited flaws hit.

Product2 known exploited9 versions
The short answer

Communications Element Manager is made by Oracle. We track 68 published vulnerabilities in it, across 9 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 23 January 2025. If you run Communications Element Manager, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Communications Element Manager 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 Communications Element Manager 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

    8.1.18.2.08.2.1
  • CVE-2020-1938Exploited list, 3 Mar 2022

    Apache Tomcat Improper Privilege Management Vulnerability

    8.1.18.2.08.2.1
Known exploited

Which Communications Element Manager vulnerabilities are being exploited?

2 flaws are 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
  2. 9.8
    CVE-2020-1938CriticalKnown exploited
    Apache Tomcat Improper Privilege Management Vulnerability

    Apache Tomcat treats Apache JServ Protocol (AJP) connections as having higher trust than, for example, a similar HTTP connection.

    Chance of use>99%Known exploited since3 Mar 2022
Exploit likelihood

Which Communications Element Manager 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%

    Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups.

    CVSS5.9Published18 Dec 2021
  2. >99%
    CVE-2020-1938CriticalKnown exploited

    When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat.

    CVSS9.8Published24 Feb 2020
  3. 97%

    A carefully crafted request body can cause a buffer overflow in the mod_lua multipart parser (r:parsebody() called from Lua scripts).

    CVSS9.8Published20 Dec 2021
  4. 90%

    Apache HTTP server 2.4.32 to 2.4.44 mod_proxy_uwsgi info disclosure and possible RCE

    CVSS9.8Published7 Aug 2020
  5. 89%

    Apache HTTP Server versions 2.4.20 to 2.4.43.

    CVSS7.5Published7 Aug 2020
  6. 89%

    In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a...

    CVSS7.5Published17 Jan 2020
  7. 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
  8. 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
  9. 82%

    A crafted URI sent to httpd configured as a forward proxy (ProxyRequests on) can cause a crash (NULL pointer dereference) or, for configurations mixing forward and reverse proxy declarations, can allow for requests...

    CVSS8.2Published20 Dec 2021
Precursor Intelligence

Running Communications Element Manager? 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 68 published vulnerabilities listed under the name Communications Element Manager, across 9 versions. The most recent Communications Element Manager flaw added to the known-exploited list is CVE-2020-11023, on 23 January 2025.

2 are on the list of flaws known to be exploited. The most recently added are CVE-2020-11023 and CVE-2020-1938.

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

Create a Precursor Intelligence account and track Communications Element Manager. 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.