# CVE-2007-1633: Path traversal in n/a

> Remote attackers can execute arbitrary code via directory traversal in the Splatt Forum module for PHP-Nuke by including malicious log files.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xj9r-4xfh-455m

## What is CVE-2007-1633?

CVE-2007-1633 is a high-severity path traversal vulnerability in n/a, published on 23 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in bbcode_ref.php in the Giorgio Ciranni Splatt Forum 4.0 RC1 module for PHP-Nuke allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the name parameter, as demonstrated by injecting PHP sequences into an Apache HTTP Server log file, which is then included by bbcode_ref.php.

## Which versions are affected by CVE-2007-1633?

It affects 1 product.


Products: Giorgio Ciranni Splatt Forum.

## How do I fix CVE-2007-1633?

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

## Is CVE-2007-1633 being exploited?

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

Public exploit code:

- PHP-Nuke Module splattforum 4.0 RC1 - Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1633 and fix it if it is affected.

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

## Sources

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

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