# CVE-2006-4679: Information disclosure in n/a

> Remote attackers can obtain sensitive information by sending a specific HTTP header to DokuWiki instances with debug mode enabled by default.

- **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:** Yes
- **Published:** 11 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-4679, GHSA-v3v7-2m7q-j6jq

## What is CVE-2006-4679?

CVE-2006-4679 is a medium-severity vulnerability in n/a, published on 11 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DokuWiki before 2006-03-09c enables the debug feature by default, which allows remote attackers to obtain sensitive information by calling doku.php with the X-DOKUWIKI-DO HTTP header set to "debug".

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

It affects 1 product.


Products: Andreas Gohr Dokuwiki.

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

Upgrade to a fixed version.

## Is CVE-2006-4679 being exploited?

There is no known exploitation of CVE-2006-4679 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-4679 and fix it if it is affected.

What it is: CVE-2006-4679 is a medium-severity vulnerability in n/a, published on 11 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4679 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-4679/ (Markdown: https://insights.sbomify.com/CVE-2006-4679/index.md)
```

## Sources

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

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