# CVE-2005-2372: File upload in n/a

> Attackers can execute arbitrary code by uploading malicious form files and referencing them via servlet parameters in Oracle Forms.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h3q5-7899-7pxx

## What is CVE-2005-2372?

CVE-2005-2372 is a high-severity vulnerability in n/a, published on 26 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Oracle Forms 4.5 through 10g starts form executables from arbitrary directories and executes them as the Oracle or System user, which allows attackers to execute arbitrary code by uploading a malicious .fmx file and referencing it using an absolute pathname argument in the (1) form or (2) module parameters to f90servlet.

## Which versions are affected by CVE-2005-2372?

It affects 1 product.


Products: Oracle Forms.

## How do I fix CVE-2005-2372?

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

## Is CVE-2005-2372 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-83099](https://insights.sbomify.com/CVE-2026-83099/): Auth bypass in Oracle Forms (critical 10.0)
- [CVE-2026-83094](https://insights.sbomify.com/CVE-2026-83094/): Auth bypass in Oracle Forms (critical 9.8)
- [CVE-2026-83095](https://insights.sbomify.com/CVE-2026-83095/): Auth bypass in Oracle Forms (critical 9.8)
- [CVE-2026-83098](https://insights.sbomify.com/CVE-2026-83098/): Auth bypass in Oracle Forms (critical 9.8)
- [CVE-2026-83100](https://insights.sbomify.com/CVE-2026-83100/): Auth bypass in Oracle Forms (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2372 and fix it if it is affected.

What it is: CVE-2005-2372 is a high-severity vulnerability in n/a, published on 26 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2372 in the wild and no public exploit code.

Affected product: n/a. 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-2005-2372/ (Markdown: https://insights.sbomify.com/CVE-2005-2372/index.md)
```

## Sources

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

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