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

> Remote attackers can execute arbitrary local files via directory traversal in the eBoard module for PHP-Nuke.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 10 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fxpj-5www-pvxp

## What is CVE-2007-1934?

CVE-2007-1934 is a medium-severity path traversal vulnerability in n/a, published on 10 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in member.php in the eBoard 1.0.7 module for PHP-Nuke allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the GLOBALS[name] parameter.

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

It affects 1 product.


Products: Php-Nuke Eboard Module.

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

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

## Is CVE-2007-1934 being exploited?

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

Public exploit code:

- PHP-Nuke Module eBoard 1.0.7 - GLOBALS[name] Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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