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

> Authenticated users can read unauthorized files in DokuWiki when Access Control Lists are enabled.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2945, GHSA-qxv2-58jf-jpc7

## What is CVE-2006-2945?

CVE-2006-2945 is a medium-severity path traversal vulnerability in n/a, published on 12 Jun 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the user profile change functionality in DokuWiki, when Access Control Lists are enabled, allows remote authenticated users to read unauthorized files via unknown attack vectors.

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

It affects 1 product.


Products: Andreas Gohr Dokuwiki.

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

Upgrade to a fixed version.

## Is CVE-2006-2945 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5099](https://insights.sbomify.com/CVE-2006-5099/): Command injection in n/a (high 7.5)
- [CVE-2006-4674](https://insights.sbomify.com/CVE-2006-4674/): Code injection in n/a (high 7.5)
- [CVE-2006-4675](https://insights.sbomify.com/CVE-2006-4675/): File upload in n/a (high 7.5)
- [CVE-2006-2878](https://insights.sbomify.com/CVE-2006-2878/): Code injection in n/a (high 7.5)
- [CVE-2004-2559](https://insights.sbomify.com/CVE-2004-2559/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2945 is a medium-severity path traversal vulnerability in n/a, published on 12 Jun 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2945 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-2945/ (Markdown: https://insights.sbomify.com/CVE-2006-2945/index.md)
```

## Sources

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

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