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

> Remote attackers can read arbitrary files via directory traversal in the class parameter of index.php or admin/index.php.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mg49-8496-7rxj

## What is CVE-2012-0996?

CVE-2012-0996 is a medium-severity path traversal vulnerability in n/a, published on 20 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in 11in1 1.2.1 stable 12-31-2011 allow remote attackers to read arbitrary files via a .. (dot dot) in the class parameter to (1) index.php or (2) admin/index.php.

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

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

It affects 1 product.


Products: 11in1 11in1.

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

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

## Is CVE-2012-0996 being exploited?

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

Public exploit code:

- 11in1 CMS 1.2.1 - 'index.php?class' Traversal Local File Inclusion (exploitdb)
- 11in1 CMS 1.2.1 - '/admin/index.php?class' Traversal Local File Inclusion (exploitdb)
- 11in1 CMS 1.2.1 - Local File Inclusion (LFI) (nuclei): http/cves/2012/CVE-2012-0996.yaml

## Other vulnerabilities in n/a

- [CVE-2012-0997](https://insights.sbomify.com/CVE-2012-0997/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0996 is a medium-severity path traversal vulnerability in n/a, published on 20 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-0996 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-0996/ (Markdown: https://insights.sbomify.com/CVE-2012-0996/index.md)
```

## Sources

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

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