# CVE-2025-50108: Missing authorization in Oracle Hyperion Financial Reporting

> Low-privileged attackers can modify or read data in Oracle Hyperion Financial Reporting via HTTP with user interaction.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-777h-4rg8-cwf5

## What is CVE-2025-50108?

CVE-2025-50108 is a medium-severity missing authorization vulnerability in Oracle Hyperion Financial Reporting, published on 15 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Hyperion Financial Reporting product of Oracle Hyperion (component: Workspace).   The supported version that is affected is 11.2.20.0.000. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hyperion Financial Reporting.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Hyperion Financial Reporting, 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 Hyperion Financial Reporting accessible data as well as  unauthorized read access to a subset of Oracle Hyperion Financial Reporting accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Hyperion Financial Reporting.

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

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

## Is CVE-2025-50108 being exploited?

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

## Other vulnerabilities in Oracle Hyperion Financial Reporting

- [CVE-2026-70739](https://insights.sbomify.com/CVE-2026-70739/): Auth bypass in Oracle Hyperion Financial Reporting (critical 9.8)
- [CVE-2026-70740](https://insights.sbomify.com/CVE-2026-70740/): Auth bypass in Oracle Hyperion Financial Reporting (critical 9.8)
- [CVE-2026-70745](https://insights.sbomify.com/CVE-2026-70745/): Auth bypass in Oracle Hyperion Financial Reporting (critical 9.8)
- [CVE-2016-3493](https://insights.sbomify.com/CVE-2016-3493/): Other in n/a (critical 9.8)
- [CVE-2026-70741](https://insights.sbomify.com/CVE-2026-70741/): Missing authorization in Oracle Hyperion Financial Reporting (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50108 is a medium-severity missing authorization vulnerability in Oracle Hyperion Financial Reporting, published on 15 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-50108 in the wild and no public exploit code.

Affected product: Oracle Hyperion Financial Reporting. 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-50108/ (Markdown: https://insights.sbomify.com/CVE-2025-50108/index.md)
```

## Sources

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

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