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

> Remote attackers can obtain sensitive path information via crafted parameters in w-agora forum software.

- **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:** 21 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vppg-qjgp-vj8p

## What is CVE-2007-0606?

CVE-2007-0606 is a medium-severity vulnerability in n/a, published on 21 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

w-agora 4.2.1 allows remote attackers to obtain sensitive information by via the (1) bn[] array parameter to index.php, which expects a string, and (2) certain parameters to delete_forum.php, which displays the path name in the resulting error message.

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

It affects 1 product.


Products: W-Agora W-Agora.

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

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

## Is CVE-2007-0606 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4867](https://insights.sbomify.com/CVE-2010-4867/): Path traversal in n/a (high 7.5)
- [CVE-2008-1466](https://insights.sbomify.com/CVE-2008-1466/): Code injection in n/a (high 7.5)
- [CVE-2007-6647](https://insights.sbomify.com/CVE-2007-6647/): SQL injection in n/a (high 7.5)
- [CVE-2007-1604](https://insights.sbomify.com/CVE-2007-1604/): File upload in n/a (high 7.5)
- [CVE-2004-1562](https://insights.sbomify.com/CVE-2004-1562/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0606 is a medium-severity vulnerability in n/a, published on 21 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0606 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-2007-0606/ (Markdown: https://insights.sbomify.com/CVE-2007-0606/index.md)
```

## Sources

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

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