Financial Services Revenue Management and Billing Analytics vulnerabilitiesAnd the versions its exploited flaws hit.
Financial Services Revenue Management and Billing Analytics is made by Oracle. We track 7 published vulnerabilities in it, across 6 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 23 January 2025. If you run Financial Services Revenue Management and Billing Analytics, check your version against the exploited flaws below and patch those first.
The most recent Financial Services Revenue Management and Billing Analytics flaw added to the known-exploited list is CVE-2020-11023, on 23 January 2025. We keep watching the known-exploited list.
Which versions of Financial Services Revenue Management and Billing Analytics 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.72.8
Which Financial Services Revenue Management and Billing Analytics 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.
- 6.9JQuery Cross-Site Scripting (XSS) Vulnerability
JQuery contains a persistent cross-site scripting (XSS) vulnerability.
Which Financial Services Revenue Management and Billing Analytics 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.
- 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-4104High
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration.
- 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.
- 28%CVE-2019-10086High
In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects.
- 14%CVE-2019-2904Critical
Vulnerability in the Oracle JDeveloper and ADF product of Oracle Fusion Middleware (component: ADF Faces).
Running Financial Services Revenue Management and Billing Analytics? 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
- Financial Services Revenue Management and Billing Analytics 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 7 published vulnerabilities listed under the name Financial Services Revenue Management and Billing Analytics, across 6 versions. The most recent Financial Services Revenue Management and Billing Analytics 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, 2.8. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Financial Services Revenue Management and Billing Analytics. 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.