VulnerabilityPublished 15 Jul 2025Updated 26 Feb 2026

CVE-2025-50060: Oracle BI Publisher · Improper Access Control

Affects Oracle BI PublisherSource CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jul 2025
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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavencom.oracle/bi-publisher`pkg:maven/com.oracle/bi-publisher`Other threats	Affected =7.6.0.0.0 =8.2.0.0.0 =12.2.1.4.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should focus on restricting network access to Oracle BI Publisher instances, limiting exposure to trusted internal networks or VPNs only. 2. Implement strict access control policies to ensure that users have only the minimum necessary privileges, reducing the risk posed by low-privileged attackers. 3. Monitor network traffic and logs for unusual HTTP requests or access patterns targeting Oracle BI Publisher endpoints. 4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests that could exploit this vulnerability. 5. Coordinate with Oracle for timely patch releases and apply official patches as soon as they become available. 6. Conduct thorough audits of Oracle BI Publisher configurations and user permissions to identify and remediate potential weaknesses. 7. Consider isolating Oracle BI Publisher servers in segmented network zones to contain potential compromises. 8. Educate administrators and security teams about the vulnerability specifics to enhance detection and response capabilities. 9. Develop and test incident response plans specifically addressing potential exploitation scenarios of this vulnerability. These targeted steps go beyond generic advice by focusing on access control tightening, network segmentation, and proactive monitoring tailored to the nature of this vulnerability.

Description

Vulnerability in the Oracle BI Publisher product of Oracle Analytics (component: Web Server). Supported versions that are affected are 7.6.0.0.0, 8.2.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle BI Publisher accessible data as well as unauthorized access to critical data or complete access to all Oracle BI Publisher accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Impact

The impact of CVE-2025-50060 is substantial for organizations using affected Oracle BI Publisher versions. Successful exploitation can lead to unauthorized creation, deletion, or modification of critical business data, potentially corrupting reports, analytics, and decision-making processes. The attacker could also gain full access to all data accessible through the BI Publisher, leading to data breaches involving sensitive corporate, financial, or personal information. This compromises confidentiality and integrity, undermining trust in business intelligence outputs and possibly violating regulatory compliance requirements. Although availability is not directly impacted, the integrity loss can cause operational disruptions and financial losses. Enterprises in finance, healthcare, government, and other sectors that rely heavily on Oracle BI Publisher for data reporting are at high risk. The ease of exploitation via network access with low privileges and no user interaction increases the threat level, potentially enabling lateral movement within networks or serving as a foothold for further attacks. The absence of known exploits in the wild currently provides a window for proactive defense, but the vulnerability’s characteristics suggest it could be rapidly weaponized once exploit code becomes available.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

oracle.com/security-alerts/cpujul2025.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 03:07 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats