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

> Remote attackers can access the users.dat file to obtain usernames and passwords due to insufficient access control.

- **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:** 26 Oct 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-69x7-h4hg-wh8p

## What is CVE-2002-2322?

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

### Official description

Ultimate PHP Board (UPB) 1.0b stores the users.dat data file under the web root with insufficient access control, which allows remote attackers to obtain usernames and passwords.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Ultimate Php Board Ultimate Php Board.

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

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

## Is CVE-2002-2322 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3203](https://insights.sbomify.com/CVE-2006-3203/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2006-6790](https://insights.sbomify.com/CVE-2006-6790/): Code injection in n/a (high 7.5)
- [CVE-2005-1615](https://insights.sbomify.com/CVE-2005-1615/): SQL injection in n/a (high 7.5)
- [CVE-2005-1616](https://insights.sbomify.com/CVE-2005-1616/): Information disclosure in n/a (high 7.5)
- [CVE-2006-7169](https://insights.sbomify.com/CVE-2006-7169/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2322 is a medium-severity vulnerability in n/a, published on 26 Oct 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-2002-2322 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-2002-2322/ (Markdown: https://insights.sbomify.com/CVE-2002-2322/index.md)
```

## Sources

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

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