Skip to main content
CISA Known Exploited Vulnerabilities

Oracle BI Publisher Unauthorized Access Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2022-03-25
Remediation due
2022-04-15

Required action
Apply updates per vendor instructions.

CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2019-2616

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).

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2019-2616 to the KEV catalog 1,067 days after its CVE record was published.
  • It is one of 46 Oracle entries in the CISA KEV catalog, and one of 22 added in 2022.
  • Its current EPSS score (92.2%) is higher than that of 74% of CISA KEV entries.

Severity

CVSS 3.1 · CISA · Base score7.2 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableyes
Technical impactpartial

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
Asset not publicly exposed
14 days
KEV due date
2022-04-15
21 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact partial, 2024-10-02).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Oracle Corporation
BI Publisher (formerly XML Publisher)
11.1.1.9.0
12.2.1.3.0
12.2.1.4.0

References

1 links

Record Details

Published
2019-04-23
Last updated
2026-01-12
Assigner (CNA)
oracle
Credited to
-

More from Oracle

All Oracle CVEs→

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.