# CVE-2004-2362: Information disclosure in n/a

> Remote attackers can obtain the physical file path of the PHPX application by sending invalid parameters, leading to information disclosure.

- **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:** 16 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fw8g-72h2-fm5r

## What is CVE-2004-2362?

CVE-2004-2362 is a medium-severity vulnerability in n/a, published on 16 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHPX 3.2.6 and earlier allows remote attackers to obtain the physical path of PHPX via a null or invalid value in the limit parameter, which leaks the pathname in a database error message, as demonstrated using forums.php.

## Which versions are affected by CVE-2004-2362?

It affects 1 product.


Products: Phpx Phpx.

## How do I fix CVE-2004-2362?

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

## Is CVE-2004-2362 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0249](https://insights.sbomify.com/CVE-2004-0249/): Auth bypass in n/a (critical 10.0)
- [CVE-2008-3489](https://insights.sbomify.com/CVE-2008-3489/): SQL injection in n/a (high 7.5)
- [CVE-2007-1550](https://insights.sbomify.com/CVE-2007-1550/): SQL injection in n/a (high 7.5)
- [CVE-2005-3968](https://insights.sbomify.com/CVE-2005-3968/): SQL injection in n/a (high 7.5)
- [CVE-2008-5000](https://insights.sbomify.com/CVE-2008-5000/): SQL injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2362 and fix it if it is affected.

What it is: CVE-2004-2362 is a medium-severity vulnerability in n/a, published on 16 Aug 2005. 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-2004-2362 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-2004-2362/ (Markdown: https://insights.sbomify.com/CVE-2004-2362/index.md)
```

## Sources

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

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