# CVE-2006-0445: Information disclosure in n/a

> Authenticated users can obtain the installation path by submitting an invalid filename to the uploader page, revealing sensitive server directory information.

- **Severity:** Medium 4.0 (`AV:N/AC:L/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:** 26 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fp6x-cwxh-3wvm

## What is CVE-2006-0445?

CVE-2006-0445 is a medium-severity vulnerability in n/a, published on 26 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

index.php in Phpclanwebsite 1.23.1 allows remote authenticated users to obtain the installation path by specifying an invalid file name to the uploader page, as demonstrated by "\", which will display the full path of uploader.php.  NOTE: this might be the result of a file inclusion vulnerability.

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

It affects 1 product.


Products: Phpclanwebsite Phpclanwebsite.

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

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

## Is CVE-2006-0445 being exploited?

There is no known exploitation of CVE-2006-0445 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-5877](https://insights.sbomify.com/CVE-2008-5877/): SQL injection in n/a (medium 6.8)
- [CVE-2006-0444](https://insights.sbomify.com/CVE-2006-0444/): SQL injection in n/a (medium 6.8)
- [CVE-2008-5878](https://insights.sbomify.com/CVE-2008-5878/): Path traversal in n/a (medium 5.1)
- [CVE-2008-5879](https://insights.sbomify.com/CVE-2008-5879/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-0366](https://insights.sbomify.com/CVE-2006-0366/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0445 is a medium-severity vulnerability in n/a, published on 26 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0445 in the wild and no public exploit code.

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

## Sources

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

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