Skip to main content
VulnerabilityPublished

CVE-2025-30750: Oracle Database Server · Incorrect Authorization

Affects Oracle Database ServerSource CVE Database V5

0

Not known to be exploited · CVSS 2.4 Low.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
2.4Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Mavencom.oracle.database/oracle-database-serverpkg:maven/com.oracle.database/oracle-database-serverOther threatsAffected
  • =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. Restrict and monitor the assignment of the Create User privilege strictly to trusted administrators and enforce the principle of least privilege.
  2. Implement robust network segmentation and access controls to limit Oracle Net access only to authorized hosts and users.
  3. Enhance user awareness training to reduce the risk of social engineering attacks that could facilitate the required human interaction for exploitation.
  4. Enable and regularly review audit logs for unusual activities related to user creation and modifications within the database.
  5. Apply Oracle's security best practices for database hardening, including using Oracle Database Vault or similar tools to enforce separation of duties.
  6. Monitor Oracle security advisories closely for patches addressing this vulnerability and plan timely deployment once available.
  7. Employ multi-factor authentication for privileged database accounts to reduce the risk of credential misuse.
  8. Consider implementing real-time alerting mechanisms for changes in audit configurations or unexpected modifications to audit data. These steps go beyond generic advice by focusing on privilege management, network access control, user interaction risk reduction, and proactive monitoring tailored to the specific conditions of this vulnerability.

Description

Vulnerability in the Unified Audit component of Oracle Database Server. Supported versions that are affected are 19.3-19.27, 21.3-21.18 and 23.4-23.8. Easily exploitable vulnerability allows high privileged attacker having Create User privilege with network access via Oracle Net to compromise Unified Audit. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Unified Audit accessible data. CVSS 3.1 Base Score 2.4 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N).

References

Community reviews

Loading reviews…