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

> Remote attackers can read arbitrary files via directory traversal in the module parameter of json.php in TomatoCart.

- **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:** 17 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2xrv-6g4w-wcv4

## What is CVE-2012-5907?

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

### Official description

Directory traversal vulnerability in json.php in TomatoCart 1.2.0 Alpha 2 and possibly earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the module parameter in a "3" action.

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

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

It affects 1 product.


Products: Tomatocart Tomatocart.

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

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

## Is CVE-2012-5907 being exploited?

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

Public exploit code:

- TomatoCart 1.2.0 Alpha 2 - 'json.php' Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-3978](https://insights.sbomify.com/CVE-2014-3978/): SQL injection in n/a (medium 6.5)
- [CVE-2011-3811](https://insights.sbomify.com/CVE-2011-3811/): Information disclosure in n/a (medium 5.0)
- [CVE-2014-3830](https://insights.sbomify.com/CVE-2014-3830/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-4934](https://insights.sbomify.com/CVE-2012-4934/): Business logic in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5907 is a medium-severity path traversal vulnerability in n/a, published on 17 Nov 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-5907 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-5907/ (Markdown: https://insights.sbomify.com/CVE-2012-5907/index.md)
```

## Sources

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

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