CVE-2024-20987: Oracle BI Publisher (formerly XML Publisher) · Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to
Affects Oracle BI Publisher (formerly XML Publisher)Source CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.oracle.bi/publisherpkg:maven/com.oracle.bi/publisherOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should implement the following specific mitigation steps: 1) Immediately identify and inventory all Oracle BI Publisher 12.2.1.4.0 instances within their environment. 2) Restrict network access to BI Publisher web interfaces using network segmentation and firewall rules, limiting exposure to trusted internal networks or VPNs only. 3) Enhance user training and awareness programs focusing on phishing and social engineering risks, emphasizing caution with unsolicited links or attachments. 4) Monitor Oracle security advisories for patches or updates addressing CVE-2024-20987 and prioritize timely application once available. 5) Implement robust logging and monitoring on BI Publisher servers to detect unusual data access or modification activities, enabling rapid incident response. 6) Employ multi-factor authentication (MFA) for accessing BI Publisher interfaces to reduce the risk of unauthorized access. 7) Review and tighten access controls and permissions within BI Publisher to ensure least privilege principles are enforced, minimizing potential damage from compromised accounts. 8) Conduct regular security assessments and penetration tests focusing on Oracle Analytics environments to identify and remediate related vulnerabilities proactively.
Description
Vulnerability in the Oracle BI Publisher product of Oracle Analytics (component: Web Server). The supported version that is affected is 12.2.1.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle BI Publisher, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle BI Publisher accessible data as well as unauthorized read access to a subset of Oracle BI Publisher accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).