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

> Remote attackers can read arbitrary files via directory traversal in the News Portal's arhiva.php script.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** 6 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6x24-hm2g-9f7x

## What is CVE-2005-4039?

CVE-2005-4039 is a high-severity path traversal vulnerability in n/a, published on 6 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 arhiva.php in Web4Future Portal Solutions News Portal allows remote attackers to read arbitrary files via the dir parameter.

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

It affects 1 product.


Products: Web4future Portal Solutions.

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

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

## Is CVE-2005-4039 being exploited?

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

Public exploit code:

- Web4Future Portal Solutions - 'Arhiva.php' Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4038](https://insights.sbomify.com/CVE-2005-4038/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4039 is a high-severity path traversal vulnerability in n/a, published on 6 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-4039 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-4039/ (Markdown: https://insights.sbomify.com/CVE-2005-4039/index.md)
```

## Sources

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

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