# CVE-2021-2158: Missing authorization in Hyperion Financial Management

> High-privileged attackers can compromise Oracle Hyperion Financial Management to read, modify, or disrupt data via HTTP.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Apr 2021
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-8335-4v5h-xm34

## What is CVE-2021-2158?

CVE-2021-2158 is a low-severity missing authorization vulnerability in Oracle Hyperion Financial Management, published on 22 Apr 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Hyperion Financial Management product of Oracle Hyperion (component: Task Automation). The supported version that is affected is 11.1.2.4. Difficult to exploit vulnerability allows high privileged attacker with network access via HTTP to compromise Hyperion Financial Management. 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 Hyperion Financial Management accessible data as well as unauthorized read access to a subset of Hyperion Financial Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Hyperion Financial Management. CVSS 3.1 Base Score 3.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L).

## Which versions are affected by CVE-2021-2158?

It affects 1 product.


Products: Oracle Hyperion Financial Management.

## How do I fix CVE-2021-2158?

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

## Is CVE-2021-2158 being exploited?

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

## Other vulnerabilities in Oracle Hyperion Financial Management

- [CVE-2026-87230](https://insights.sbomify.com/CVE-2026-87230/): Missing authorization in Oracle Hyperion Financial Management (critical 10.0)
- [CVE-2026-70921](https://insights.sbomify.com/CVE-2026-70921/): Missing authorization in Oracle Hyperion Financial Management (critical 10.0)
- [CVE-2012-1714](https://insights.sbomify.com/CVE-2012-1714/): Code injection in n/a (critical 10.0)
- [CVE-2026-87172](https://insights.sbomify.com/CVE-2026-87172/): Privilege escalation in Oracle Hyperion Financial Management (critical 9.9)
- [CVE-2026-70920](https://insights.sbomify.com/CVE-2026-70920/): Auth bypass in Oracle Hyperion Financial Management (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-2158 and fix it if it is affected.

What it is: CVE-2021-2158 is a low-severity missing authorization vulnerability in Oracle Hyperion Financial Management, published on 22 Apr 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-2158 in the wild and no public exploit code.

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

## Sources

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

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