# CVE-2007-6502: Information disclosure in n/a

> Authenticated users can obtain sensitive information like usernames and directory paths via specific parameters and requests in Hosting Controller.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:P/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:** 20 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w8pg-v9h6-284r

## What is CVE-2007-6502?

CVE-2007-6502 is a medium-severity vulnerability in n/a, published on 20 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hosting Controller 6.1 Hot fix 3.3 and earlier allows remote authenticated users to obtain sensitive information via (1) the AdminName and AdminLevel parameters to fp2000/NEWSRVR.asp, which discloses usernames; and (2) certain XML HTTP requests to hosting/css.asp using Microsoft.XMLHTTP or MSXML2.XMLHTTP objects, which trigger a response with the setup directory pathname in the HTML source; and (3) might allow remote attackers to obtain sensitive information via a request for /admin/forum/, which reveals the path in an error message when a forum is not found.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2007-6502?

It affects 1 product.


Products: Hosting Controller Hosting Controller.

## How do I fix CVE-2007-6502?

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

## Is CVE-2007-6502 being exploited?

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

Public exploit code:

- hosting controller 6.1 hot fix 3.3 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-6494](https://insights.sbomify.com/CVE-2007-6494/): Auth bypass in n/a (critical 10.0)
- [CVE-2002-0773](https://insights.sbomify.com/CVE-2002-0773/): Path traversal in n/a (critical 10.0)
- [CVE-2002-0774](https://insights.sbomify.com/CVE-2002-0774/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2002-0465](https://insights.sbomify.com/CVE-2002-0465/): Path traversal in n/a (critical 10.0)
- [CVE-2006-1764](https://insights.sbomify.com/CVE-2006-1764/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6502 and fix it if it is affected.

What it is: CVE-2007-6502 is a medium-severity vulnerability in n/a, published on 20 Dec 2007. Any signed-in user can exploit it 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-2007-6502 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-2007-6502/ (Markdown: https://insights.sbomify.com/CVE-2007-6502/index.md)
```

## Sources

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

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