# CVE-2003-0599: Path traversal in n/a

> An attacker can potentially access files outside the intended directory due to VFS path configuration issues in phpGroupWare.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 25 Jul 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jpqw-hvvp-v47x

## What is CVE-2003-0599?

CVE-2003-0599 is a critical path traversal vulnerability in n/a, published on 25 Jul 2003. It can be exploited over the network.

### Official description

Unknown vulnerability in the Virtual File System (VFS) capability for phpGroupWare 0.9.16preRC and versions before 0.9.14.004 with unknown implications, related to the VFS path being under the web document root.

## Which versions are affected by CVE-2003-0599?

It affects 1 product.


Products: Phpgroupware Phpgroupware.

## How do I fix CVE-2003-0599?

Upgrade to a fixed version.

## Is CVE-2003-0599 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2406](https://insights.sbomify.com/CVE-2004-2406/): Other in n/a (critical 10.0)
- [CVE-2004-2407](https://insights.sbomify.com/CVE-2004-2407/): Unknown vulnerability in phpGroupWare before 0.9.14.002 has unknown attack vectors and impact, related to a "security hole" in the Setup/Config functionality. (critical 10.0)
- [CVE-2001-0043](https://insights.sbomify.com/CVE-2001-0043/): Code injection in n/a (critical 10.0)
- [CVE-2010-0404](https://insights.sbomify.com/CVE-2010-0404/): SQL injection in n/a (high 7.5)
- [CVE-2009-4415](https://insights.sbomify.com/CVE-2009-4415/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0599 and fix it if it is affected.

What it is: CVE-2003-0599 is a critical path traversal vulnerability in n/a, published on 25 Jul 2003. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2003-0599 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-2003-0599/ (Markdown: https://insights.sbomify.com/CVE-2003-0599/index.md)
```

## Sources

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

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