CVE-2018-2958 json
Vulnerability in the BI Publisher component of Oracle Fusion Middleware (subcomponent: BI Publisher Security).
published 2018-07-18 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-14813
- cvss
- 8.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Vulnerability in the BI Publisher component of Oracle Fusion Middleware (subcomponent: BI Publisher Security). Supported versions that are affected are 11.1.1.7.0, 11.1.1.9.0, 12.2.1.2.0 and 12.2.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise BI Publisher. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all BI Publisher accessible data as well as unauthorized read access to a subset of BI Publisher accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N).
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
2.07% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.2 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Affected products
- Oracle Corporation BI Publisher (formerly XML Publisher)
References
-
oracle.com
/technetwork/security-advisory/cpujul2018-4258247.html
patch, vendor-advisory
-
securitytracker.com
/id/1041310
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/104767
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-2958
- NVD CVE-2018-2958
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.