CVE-2019-2616
HighExploitedPublic exploitEasily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise BI Publisher (formerly XML Publisher).
Published Apr 23, 2019 · Updated Jan 13, 2026
Key Facts
Patch immediately- CVE-2019-2616 is a high-severity vulnerability (CVSS 7.2 v3.1) affecting Business Intelligence Publisher (Oracle), BI Publisher (formerly XML Publisher).
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 25, 2022. Public exploit code is available.
- EPSS estimates a 92% probability of exploitation in the next 30 days.
- No fixed version is listed yet; check the vendor advisory for mitigations.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
7.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS (30-day exploit likelihood)
92%
Higher than 99.8% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2019-2616 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
Vulnerability in the BI Publisher (formerly XML Publisher) component of Oracle Fusion Middleware (subcomponent: BI Publisher Security). Supported versions that are affected are 11.1.1.9.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise BI Publisher (formerly XML Publisher). While the vulnerability is in BI Publisher (formerly XML Publisher), attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of BI Publisher (formerly XML Publisher) accessible data as well as unauthorized read access to a subset of BI Publisher (formerly XML Publisher) accessible data. CVSS 3.0 Base Score 7.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N).
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Mar 25, 2022 | Apr 15, 2022 | Not reported |
| Industry KEV feed | Mar 25, 2022 | Apr 15, 2022 | Not reported |
| CIRCL KEV | Mar 25, 2022 | Apr 15, 2022 | Not reported |
| ENISA EUVD | Mar 25, 2022 | n/a | Not reported |
Required action: Apply updates per vendor instructions.
Affected Products
4 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Business Intelligence PublisherOracle | 11.1.1.9.0, 12.2.1.3.0, 12.2.1.4.0 | n/a |
| BI Publisher (formerly XML Publisher) | >= 11.1.1.9.0 | n/a |
Timeline
Publicly disclosed
Apr 23, 2019
Added to CISA KEV
Mar 25, 2022
Added to Industry KEV feed
Mar 25, 2022
Added to CIRCL KEV
Mar 25, 2022
Added to ENISA EUVD
Mar 25, 2022
Last updated
Jan 13, 2026
References
- patchhttp://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
FAQ
Common Questions.
Vulnerability in the BI Publisher (formerly XML Publisher) component of Oracle Fusion Middleware (subcomponent: BI Publisher Security).
Affected: Business Intelligence Publisher (Oracle) versions 11.1.1.9.0, 12.2.1.3.0, 12.2.1.4.0; BI Publisher (formerly XML Publisher) versions >= 11.1.1.9.0. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 25, 2022.
Yes. It was added on Mar 25, 2022 with a federal remediation due date of Apr 15, 2022.
Public exploit code is available.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2019-2616 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo