Exploited CVEs / Oracle / CVE-2019-2616

CVE-2019-2616

Oracle BI Publisher Unauthorized Access Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-04-15 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Oracle Critical Patch Updates, linked below.

Risk summary

HighCISA KEV

7.2

CVSS base

92%

EPSS exploit probability

High

Severity

2022-03-25

Added to KEV

2022-04-15 (past due)

CISA due date

Actively exploited Oracle BI Publisher (Formerly XML Publisher) vulnerability, High severity, CVSS 7.2. Added to the CISA KEV catalog 2022-03-25.

Senserva AI read on CVE-2019-2616 CISA required action Official fix for CVE-2019-2616 Admin questions

Senserva AI Opinion for CVE-2019-2616

CVE-2019-2616 is an authentication bypass in Oracle BI Publisher (formerly XML Publisher) that lets attackers take unauthorized actions without valid credentials. Anyone running an internet-reachable BI Publisher instance is exposed, and with a 92% EPSS score plus confirmed CISA KEV listing since 2022-03-25, active exploitation is not theoretical. This is a reporting and analytics component, so a bypass can expose sensitive business data and reports.

Do this: Apply the relevant Oracle Critical Patch Update to your BI Publisher deployment and restrict its exposure to the public internet until patched.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2019-2616

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2019-2616, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2019-2616.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2019-2616: Oracle BI Publisher Unauthorized Access Vulnerability
- Affected: Oracle BI Publisher (Formerly XML Publisher)
- Severity: High, CVSS 7.2; EPSS 30-day exploitation probability 92%
- Added to CISA KEV: 2022-03-25; federal remediation due 2022-04-15
- Ransomware-linked: no
- CISA required action: Apply updates per vendor instructions.
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

The fix ships from the vendor: Oracle Critical Patch Updates.

Do this now: Federal remediation deadline 2022-04-15; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2019-2616

Published: 2022-03-25
Last revised: 2022-03-25
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

2022-03-25 added to the CISA KEV catalog by CISA
2026-07-17 CVSS 0.0 to 7.2; EPSS first scored at 92.2%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2022-04-15 (past due).

Apply updates per vendor instructions.

Official fix for CVE-2019-2616

The authoritative fix and affected-version list are published by the vendor. Find the BI Publisher (Formerly XML Publisher) advisory on Oracle Critical Patch Updates.

Oracle Critical Patch Updates CISA KEV entry

Common questions about CVE-2019-2616

Is CVE-2019-2616 actively exploited?

Yes. CVE-2019-2616 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 92%.

What is the CISA deadline and required action for CVE-2019-2616?

CISA set the federal (BOD 22-01) remediation due date at 2022-04-15, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply updates per vendor instructions.

What fixes CVE-2019-2616?

The authoritative fix is in the vendor advisory: see Oracle Critical Patch Updates for the patched BI Publisher (Formerly XML Publisher) versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2019-2616?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2019-2616's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited Oracle CVEs: CVE-2026-46817 CVE-2026-35273 CVE-2024-21182 CVE-2025-61757 CVE-2025-61884 CVE-2025-61882 CVE-2024-20953 CVE-2020-2883
All Oracle exploited CVEs on one page: Oracle vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.