# CVE-2026-60630: Missing authorization in Oracle APEX

> Low-privileged attackers can access critical Oracle APEX data due to missing authorization checks in the installation component.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-cpgq-2w42-46r2

## What is CVE-2026-60630?

CVE-2026-60630 is a medium-severity missing authorization vulnerability in Oracle APEX, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in Oracle APEX (component: Installation).  Supported versions that are affected are 24.1, 24.2 and  26.1. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle APEX executes to compromise Oracle APEX.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle APEX accessible data. CVSS 3.1 Base Score 5.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-60630?

It affects 1 product.


Products: Oracle Apex.

## How do I fix CVE-2026-60630?

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

## Is CVE-2026-60630 being exploited?

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

## Other vulnerabilities in Oracle APEX

- [CVE-2006-5352](https://insights.sbomify.com/CVE-2006-5352/): Other in n/a (critical 10.0)
- [CVE-2006-5351](https://insights.sbomify.com/CVE-2006-5351/): Other in n/a (critical 9.0)
- [CVE-2007-3860](https://insights.sbomify.com/CVE-2007-3860/): SQL injection in n/a (high 7.5)
- [CVE-2006-7138](https://insights.sbomify.com/CVE-2006-7138/): SQL injection in n/a (medium 6.0)
- [CVE-2007-3854](https://insights.sbomify.com/CVE-2007-3854/): SQL injection in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60630 and fix it if it is affected.

What it is: CVE-2026-60630 is a medium-severity missing authorization vulnerability in Oracle APEX, published on 21 Jul 2026. 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-2026-60630 in the wild and no public exploit code.

Affected product: Oracle APEX. 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-2026-60630/ (Markdown: https://insights.sbomify.com/CVE-2026-60630/index.md)
```

## Sources

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

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