Business Intelligence vulnerabilitiesAnd the versions its exploited flaws hit.
Business Intelligence is made by Oracle. We track 81 published vulnerabilities listed under that exact name, across 14 versions. 3 of them are on the list of flaws known to be exploited, the newest added on 23 January 2025. Oracle lists newer releases under their own names, such as Business Intelligence Publisher, so check those pages too.
The most recent Business Intelligence flaw added to the known-exploited list is CVE-2020-11023, on 23 January 2025. We keep watching the known-exploited list.
Is Business Intelligence listed under other names? Yes.
Oracle also lists Business Intelligence under more specific names, such as Business Intelligence Publisher. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of Business Intelligence do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
Which Business Intelligence vulnerabilities are being exploited?
3 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.
- 6.9JQuery Cross-Site Scripting (XSS) Vulnerability
JQuery contains a persistent cross-site scripting (XSS) vulnerability.
- 7.5Oracle Business Intelligence Enterprise Edition Path Transversal
Path traversal vulnerability, where an attacker can target the preview FilePath parameter of the getPreviewImage function to get access to arbitrary system file.
- 9.8Apache Struts Remote Code Execution Vulnerability
Forced Object-Graph Navigation Language (OGNL) evaluation in Apache Struts, when evaluated on raw user input in tag attributes, can lead to remote code execution.
Which Business Intelligence 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.
- >99%CVE-2021-45105Medium
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.
- 97%
Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Fusion Middleware (component: Installation).
- 96%
Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.
- 85%
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.
- 81%CVE-2021-2456Critical
Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Fusion Middleware (component: Analytics Web General).
- 81%CVE-2021-4104High
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration.
- 71%CVE-2020-2950Critical
Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Fusion Middleware (component: Analytics Web General).
- 67%CVE-2022-23305Critical
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout.
- 64%CVE-2022-23302High
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker...
- 54%CVE-2022-23307High
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw.
Running Business Intelligence? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 flaw being exploited affects software Acme tracks
JQuery contains a persistent cross-site scripting (XSS) vulnerability. When passing maliciously formed, untrusted input enclosed in HTML tags, JQuery's DOM manipulators can execute untrusted code in the context of the user's browser.
- Matched to
- Business Intelligence on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 81 published vulnerabilities listed under the name Business Intelligence, across 14 versions. The most recent Business Intelligence flaw added to the known-exploited list is CVE-2020-11023, on 23 January 2025.
3 are on the list of flaws known to be exploited. The most recently added are CVE-2020-11023, CVE-2020-14864 and CVE-2020-17530.
Oracle also lists Business Intelligence under more specific names, such as Business Intelligence Publisher. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Business Intelligence. 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.