# CVE-2002-0352: Information disclosure in n/a

> Remote attackers can view email addresses of active users via an unauthenticated request to stats.php in Phorum.

- **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:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xx6x-gw8p-x62c

## What is CVE-2002-0352?

CVE-2002-0352 is a medium-severity vulnerability in Phorum Phorum, published on 3 May 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Phorum 3.3.2 allows remote attackers to determine the email addresses of the 10 most active users via a direct HTTP request to the stats.php program, which does not require authentication.

## Which versions are affected by CVE-2002-0352?

It affects 1 product.


Products: Phorum Phorum.

## How do I fix CVE-2002-0352?

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

## Is CVE-2002-0352 being exploited?

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

## Other vulnerabilities in Phorum Phorum

- [CVE-2003-1487](https://insights.sbomify.com/CVE-2003-1487/): Command injection in n/a (critical 10.0)
- [CVE-2003-1466](https://insights.sbomify.com/CVE-2003-1466/): Server-side request forgery in n/a (high 7.5)
- [CVE-2007-2338](https://insights.sbomify.com/CVE-2007-2338/): Cross-site request forgery in n/a (high 7.5)
- [CVE-2007-2339](https://insights.sbomify.com/CVE-2007-2339/): SQL injection in n/a (high 7.5)
- [CVE-2006-6550](https://insights.sbomify.com/CVE-2006-6550/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0352 and fix it if it is affected.

What it is: CVE-2002-0352 is a medium-severity vulnerability in Phorum Phorum, published on 3 May 2002. 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-2002-0352 in the wild and no public exploit code.

Affected product: Phorum Phorum. 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-2002-0352/ (Markdown: https://insights.sbomify.com/CVE-2002-0352/index.md)
```

## Sources

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

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