# CVE-2006-4767: Path traversal in n/a

> Remote attackers can read or write arbitrary local files via directory traversal in Stefan Ernst Newsscript.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jh92-f8qg-mfp3

## What is CVE-2006-4767?

CVE-2006-4767 is a medium-severity path traversal vulnerability in n/a, published on 13 Sep 2006. It can be exploited over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Stefan Ernst Newsscript (aka WM-News) 0.5beta allow remote attackers to (1) read arbitrary local files via a .. (dot dot) sequence in the ide parameter in modify.php and (2) write to arbitrary local files via a .. sequence in the var parameter in add_go.php.  NOTE: the provenance of this information is unknown; the details are obtained from third party information.

## Which versions are affected by CVE-2006-4767?

It affects 1 product.


Products: Stefan Ernst Newsscript.

## How do I fix CVE-2006-4767?

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

## Is CVE-2006-4767 being exploited?

There is no known exploitation of CVE-2006-4767 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-4666](https://insights.sbomify.com/CVE-2006-4666/): Code injection in n/a (high 7.5)
- [CVE-2006-4766](https://insights.sbomify.com/CVE-2006-4766/): Path traversal in n/a (medium 5.0)
- [CVE-2006-4768](https://insights.sbomify.com/CVE-2006-4768/): Code injection in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4767 and fix it if it is affected.

What it is: CVE-2006-4767 is a medium-severity path traversal vulnerability in n/a, published on 13 Sep 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4767 in the wild and no public exploit code.

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

## Sources

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

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