VulnerabilityPublished 15 Apr 2025Updated 26 Feb 2026

CVE-2025-30701: Oracle Database Server · Easily exploitable vulnerability allows low privileged attacker having User Account privilege with

Affects Oracle Database ServerSource CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.3High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 42% 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:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 Apr 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.database/oracle-database-server`pkg:maven/com.oracle.database/oracle-database-server`Other threats	Affected =19.3 =21.3 =23.4	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. Apply Oracle's security patches immediately once they become available for the affected versions to remediate the vulnerability. 2. Restrict network access to Oracle Net services to trusted hosts and networks only, using firewalls and network segmentation to minimize exposure. 3. Enforce the principle of least privilege by reviewing and limiting user account permissions, ensuring users have only the necessary access rights. 4. Implement multi-factor authentication (MFA) for all database user accounts to reduce the risk of credential compromise. 5. Conduct user awareness training focused on recognizing and preventing social engineering and phishing attacks, as exploitation requires human interaction. 6. Monitor database logs and network traffic for unusual activities indicative of privilege escalation or unauthorized data modifications. 7. Use Oracle Database security features such as auditing, data encryption, and strong access controls to enhance protection. 8. Regularly review and update incident response plans to include scenarios involving database privilege escalation and data integrity attacks.

Description

Vulnerability in the RAS Security component of Oracle Database Server. Supported versions that are affected are 19.3-19.26, 21.3-21.17 and 23.4-23.7. Easily exploitable vulnerability allows low privileged attacker having User Account privilege with network access via Oracle Net to compromise RAS Security. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all RAS Security accessible data as well as unauthorized access to critical data or complete access to all RAS Security accessible data. CVSS 3.1 Base Score 7.3 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

Impact

The vulnerability allows attackers with low-level user accounts and network access to escalate their privileges and manipulate critical data within Oracle Database Server environments. This can lead to unauthorized data creation, deletion, or modification, potentially compromising the integrity and confidentiality of sensitive business information. Organizations could face data breaches, regulatory compliance violations, and operational disruptions due to corrupted or manipulated data. Since the attack requires human interaction, social engineering tactics could be leveraged to trick legitimate users into enabling the exploit, increasing the risk of insider threats or phishing campaigns. The absence of availability impact means systems remain operational, but the integrity and confidentiality compromise can have severe downstream effects on decision-making, financial reporting, and customer trust. The widespread use of Oracle Database Server in enterprises worldwide makes this vulnerability a critical concern for sectors such as finance, healthcare, government, and technology.

CWE-276Incorrect Default Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
During installation, installed file permissions are set to allow anyone to modify those files.
Architecture and Design · Operation
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
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
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 20:04 UTC

WeaknessesCWE-276

Technical details

References

Community reviews

Related threats