# CVE-2006-7099: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in SolarPay's index.php read parameter.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-46x9-v8r9-p8g6

## What is CVE-2006-7099?

CVE-2006-7099 is a medium-severity path traversal vulnerability in n/a, published on 3 Mar 2007. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in SolarPay allows remote attackers to read certain files via a .. (dot dot) in the read parameter.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2006-7099?

It affects 1 product.


Products: Solarpay Solarpay.

## How do I fix CVE-2006-7099?

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

## Is CVE-2006-7099 being exploited?

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

Public exploit code:

- SolarPay - 'index.php' Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7099 and fix it if it is affected.

What it is: CVE-2006-7099 is a medium-severity path traversal vulnerability in n/a, published on 3 Mar 2007. It can be exploited 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-2006-7099 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-2006-7099/ (Markdown: https://insights.sbomify.com/CVE-2006-7099/index.md)
```

## Sources

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

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