# CVE-2025-50107: Missing authorization in Oracle Universal Work Queue

> Unauthenticated attackers can modify or read Oracle Universal Work Queue data via HTTP, requiring user interaction to exploit.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2025
- **Updated:** 16 Jul 2025
- **Also known as:** GHSA-88hc-hf3g-2qmg

## What is CVE-2025-50107?

CVE-2025-50107 is a medium-severity missing authorization vulnerability in Oracle Universal Work Queue, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Universal Work Queue product of Oracle E-Business Suite (component: Request handling).  Supported versions that are affected are 12.2.5-12.2.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Universal Work Queue.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Universal Work Queue, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Universal Work Queue accessible data as well as  unauthorized read access to a subset of Oracle Universal Work Queue accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Universal Work Queue.

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

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

## Is CVE-2025-50107 being exploited?

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

## Other vulnerabilities in Oracle Universal Work Queue

- [CVE-2026-46963](https://insights.sbomify.com/CVE-2026-46963/): Auth bypass in Oracle Universal Work Queue (critical 9.9)
- [CVE-2026-46964](https://insights.sbomify.com/CVE-2026-46964/): Auth bypass in Oracle Universal Work Queue (critical 9.9)
- [CVE-2026-46824](https://insights.sbomify.com/CVE-2026-46824/): Auth bypass in Oracle Universal Work Queue (critical 9.9)
- [CVE-2020-14855](https://insights.sbomify.com/CVE-2020-14855/): Auth bypass in Universal Work Queue (critical 9.8)
- [CVE-2026-46965](https://insights.sbomify.com/CVE-2026-46965/): Missing authorization in Oracle Universal Work Queue (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50107 is a medium-severity missing authorization vulnerability in Oracle Universal Work Queue, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-50107 in the wild and no public exploit code.

Affected product: Oracle Universal Work Queue. 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-50107/ (Markdown: https://insights.sbomify.com/CVE-2025-50107/index.md)
```

## Sources

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

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