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

> Remote attackers can read arbitrary files via path traversal in the viewpage.php addon for PHP-Nuke.

- **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:** 28 Feb 2008
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-84fg-2wf6-cxj7

## What is CVE-2003-1545?

CVE-2003-1545 is a medium-severity path traversal vulnerability in n/a, published on 28 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Absolute path traversal vulnerability in nukestyles.com viewpage.php addon for PHP-Nuke allows remote attackers to read arbitrary files via a full pathname in the file parameter.  NOTE: This was originally reported as an issue in PHP-Nuke 6.5, but this is an independent addon.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Nukestyles Viewpage, Phpnuke Nukestyles Viewpage Module.

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

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

## Is CVE-2003-1545 being exploited?

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

Public exploit code:

- PHP-Nuke 6.5 Addon - 'Viewpage.php' File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1545 is a medium-severity path traversal vulnerability in n/a, published on 28 Feb 2008. 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-2003-1545 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-2003-1545/ (Markdown: https://insights.sbomify.com/CVE-2003-1545/index.md)
```

## Sources

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

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