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

> Remote attackers can exploit directory traversal in LinPHA to include arbitrary files, leading to arbitrary code execution via log file injection.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 15 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qw8v-6298-7825

## What is CVE-2006-0713?

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

### Official description

Directory traversal vulnerability in LinPHA 1.0 allows remote attackers to include arbitrary files via .. (dot dot) sequences in the (1) lang parameter in docs/index.php and the language parameter in (2) install/install.php, (3) install/sec_stage_install.php, (4) install/third_stage_install.php, and (5) install/forth_stage_install.php.  NOTE: direct static code injection is resultant from this issue, as demonstrated by inserting PHP code into the username, which is inserted into linpha.log, which is accessible from the directory traversal.

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

It affects 1 product.


Products: Linpha Linpha.

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

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

## Is CVE-2006-0713 being exploited?

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

Public exploit code:

- LinPHA 0.9.x/1.0 - 'lang' Local File Inclusion (exploitdb)
- LinPHA 0.9.x/1.0 - 'install.php' Local File Inclusion (exploitdb)
- LinPHA 0.9.x/1.0 - 'sec_stage_install.php' Local File Inclusion (exploitdb)
- LinPHA 0.9.x/1.0 - 'forth_stage_install.php' Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-4053](https://insights.sbomify.com/CVE-2007-4053/): SQL injection in n/a (high 7.5)
- [CVE-2004-2066](https://insights.sbomify.com/CVE-2004-2066/): SQL injection in n/a (high 7.5)
- [CVE-2006-1924](https://insights.sbomify.com/CVE-2006-1924/): SQL injection in n/a (medium 6.4)
- [CVE-2006-1923](https://insights.sbomify.com/CVE-2006-1923/): Cross-site scripting in n/a (medium 5.8)
- [CVE-2008-1856](https://insights.sbomify.com/CVE-2008-1856/): Path traversal in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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