CVE-2019-2616: Oracle BI Publisher Unauthorized Access
Oracle BI Publisher (Formerly XML Publisher) · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-25.
- CVSS v3.1 (CISA ADP)
- 7.2
- high
- EPSS (exploit probability, 30 days)
- 92%
- higher than 99.8% of all CVEs
- Added to CISA KEV
- 2022-03-25
- US federal due date 2022-04-15
- Automatable (CISA SSVC)
- yes
- technical impact: partial
CVE-2019-2616 explained
CVE-2019-2616 is an unauthorized access vulnerability in the BI Publisher Security subcomponent of Oracle BI Publisher (formerly XML Publisher), part of Oracle Fusion Middleware. An unauthenticated attacker with network access over HTTP can read and modify some BI Publisher data. CISA lists it as known to be exploited, so affected servers need prompt patching.
Impact
An unauthenticated remote attacker can exploit this flaw over HTTP with low complexity and no user interaction. Successful attacks allow unauthorized update, insert or delete access to some BI Publisher data and read access to a subset of it. The scope is changed, so attacks may significantly impact additional products. Availability is not affected. CISA rates it automatable with partial technical impact, and attackers are known to exploit it.
Who is affected
The CVE record lists Oracle Corporation BI Publisher (formerly XML Publisher) versions 11.1.1.9.0, 12.2.1.3.0 and 12.2.1.4.0 as affected. These are the supported versions named by Oracle. The CVE record names no fixed version. Refer to Oracle's vendor advisory for the patches that address this vulnerability.
Written with AI from the data on this page and checked against it automatically.
Official 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).
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Oracle Corporation BI Publisher (formerly XML Publisher)AffectedFixed in
- 11.1.1.9.0
- 12.2.1.3.0
- 12.2.1.4.0
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Oracle Corporation BI Publisher (formerly XML Publisher) |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: oracle.com/technetwork/security-advisory/cpuapr2019-50728…
- CISA's deadline for US federal agencies: 2022-04-15 (passed) – a useful benchmark for everyone else, too.
What to do
- Identify all BI Publisher installations running
11.1.1.9.0,12.2.1.3.0or12.2.1.4.0. - Apply the updates from Oracle's vendor advisory, as CISA's required action states.
- Restrict network access to BI Publisher so it is not reachable from the internet or untrusted networks.
- Review BI Publisher data and logs for unauthorized changes or access, since exploitation is known.
The CVE record names no fixed version, but this does not mean no fix exists. Follow CISA's required action and apply updates per Oracle's vendor instructions in the advisory. Until patched, limit HTTP access to BI Publisher to trusted networks and monitor for unauthorized data changes.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Partial – limited control or information
Questions about CVE-2019-2616
- Is CVE-2019-2616 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-25, with a US federal due date of 2022-04-15. Whether it has been used in ransomware campaigns is unknown.
- Does an attacker need credentials?
- No. The vulnerability can be exploited by an unauthenticated attacker with network access via HTTP, without user interaction.
- Which version should we update to?
- The CVE record does not name a fixed version. Apply the updates Oracle provides in its vendor advisory for the affected versions
11.1.1.9.0,12.2.1.3.0and12.2.1.4.0.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.