# CVE-2005-3948: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in PHPAlbum, exposing sensitive data without authentication.

- **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:** 1 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3876-89hf-c4pw

## What is CVE-2005-3948?

CVE-2005-3948 is a medium-severity path traversal vulnerability in n/a, published on 1 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in main.php in PHPAlbum 0.2.3 and earlier allows remote attackers to read arbitrary files via the (1) cmd and (2) var1 parameters.

## Which versions are affected by CVE-2005-3948?

It affects 1 product.


Products: Phpalbum.net Phpalbum.

## How do I fix CVE-2005-3948?

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

## Is CVE-2005-3948 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3948 exists.

Public exploit code:

- PHP Photo Album 0.2.3/4.1 - Local File Inclusion (exploitdb)
- PHP Photo Album 0.4.1.16 - Multiple Disclosure Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1456](https://insights.sbomify.com/CVE-2007-1456/): Code injection in n/a (high 7.5)
- [CVE-2006-4498](https://insights.sbomify.com/CVE-2006-4498/): Code injection in n/a (high 7.5)
- [CVE-2006-6613](https://insights.sbomify.com/CVE-2006-6613/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3948 and fix it if it is affected.

What it is: CVE-2005-3948 is a medium-severity path traversal vulnerability in n/a, published on 1 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3948 exists.

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-2005-3948/ (Markdown: https://insights.sbomify.com/CVE-2005-3948/index.md)
```

## Sources

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

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