# CVE-2012-0991: Path traversal in n/a

> Authenticated attackers can read arbitrary files on the server via directory traversal in OpenEMR form handling scripts.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **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:** 7 Feb 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f3x3-49j2-r3jp

## What is CVE-2012-0991?

CVE-2012-0991 is a low-severity path traversal vulnerability in n/a, published on 7 Feb 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in OpenEMR 4.1.0 allow remote authenticated users to read arbitrary files via a .. (dot dot) in the formname parameter to (1) contrib/acog/print_form.php; or (2) load_form.php, (3) view_form.php, or (4) trend_form.php in interface/patient_file/encounter.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2012-0991?

It affects 1 product.


Products: Openemr Openemr.

## How do I fix CVE-2012-0991?

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

## Is CVE-2012-0991 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-0991 exists.

Public exploit code:

- OpenEMR 4.1 - '/Interface/patient_file/encounter/trend_form.php?formname' Traversal Local File Inclusion (exploitdb)
- OpenEMR 4.1 - '/Interface/patient_file/encounter/load_form.php?formname' Traversal Local File Inclusion (exploitdb)
- OpenEMR 4.1 - '/contrib/acog/print_form.php?formname' Traversal Local File Inclusion (exploitdb)
- OpenEMR 4.1 - Local File Inclusion (nuclei): http/cves/2012/CVE-2012-0991.yaml

## Other vulnerabilities in n/a

- [CVE-2012-0992](https://insights.sbomify.com/CVE-2012-0992/): Command injection in n/a (high 8.5)
- [CVE-2006-5795](https://insights.sbomify.com/CVE-2006-5795/): File upload in n/a (high 7.5)
- [CVE-2006-5811](https://insights.sbomify.com/CVE-2006-5811/): Code injection in n/a (medium 6.8)
- [CVE-2006-2929](https://insights.sbomify.com/CVE-2006-2929/): Code injection in n/a (medium 6.8)
- [CVE-2007-0649](https://insights.sbomify.com/CVE-2007-0649/): Code injection in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0991 and fix it if it is affected.

What it is: CVE-2012-0991 is a low-severity path traversal vulnerability in n/a, published on 7 Feb 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-0991 exists.

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-2012-0991/ (Markdown: https://insights.sbomify.com/CVE-2012-0991/index.md)
```

## Sources

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

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