# CVE-2025-21578: Missing authorization in Oracle Secure Backup

> High-privileged attackers can compromise Oracle Secure Backup via improper access control, leading to full system takeover.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-xx97-cmjp-pm7g

## What is CVE-2025-21578?

CVE-2025-21578 is a medium-severity missing authorization vulnerability in Oracle Secure Backup, published on 15 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in Oracle Secure Backup (component: General).  Supported versions that are affected are 12.1.0.1, 12.1.0.2, 12.1.0.3, 18.1.0.0, 18.1.0.1 and  18.1.0.2. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle Secure Backup executes to compromise Oracle Secure Backup.  Successful attacks of this vulnerability can result in takeover of Oracle Secure Backup. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-21578?

It affects 1 product.


Products: Oracle Secure Backup.

## How do I fix CVE-2025-21578?

No fix has been published for CVE-2025-21578 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-21578 being exploited?

There is no known exploitation of CVE-2025-21578 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Secure Backup

- [CVE-2011-2261](https://insights.sbomify.com/CVE-2011-2261/): Other in n/a (critical 10.0)
- [CVE-2010-0898](https://insights.sbomify.com/CVE-2010-0898/): Other in n/a (critical 10.0)
- [CVE-2010-0907](https://insights.sbomify.com/CVE-2010-0907/): Other in n/a (critical 10.0)
- [CVE-2010-0072](https://insights.sbomify.com/CVE-2010-0072/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1977](https://insights.sbomify.com/CVE-2009-1977/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-21578 and fix it if it is affected.

What it is: CVE-2025-21578 is a medium-severity missing authorization vulnerability in Oracle Secure Backup, published on 15 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-21578 in the wild and no public exploit code.

Affected product: Oracle Secure Backup. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-21578/ (Markdown: https://insights.sbomify.com/CVE-2025-21578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-21578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-21578
- OSV: https://osv.dev/vulnerability/CVE-2025-21578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-21578/
Summaries are generated and may contain mistakes; the official description above is the record.