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

> Remote attackers can access sensitive source code files in WordPress directories without authentication, leading to information disclosure.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 3 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-0986, GHSA-6vgm-3w54-5w82

## What is CVE-2006-0986?

CVE-2006-0986 is a medium-severity vulnerability in Wordpress Wordpress, published on 3 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress 2.0.1 and earlier allows remote attackers to obtain sensitive information via a direct request to (1) default-filters.php, (2) template-loader.php, (3) rss-functions.php, (4) locale.php, (5) wp-db.php, and (6) kses.php in the wp-includes/ directory; and (7) edit-form-advanced.php, (8) admin-functions.php, (9) edit-link-form.php, (10) edit-page-form.php, (11) admin-footer.php, and (12) menu.php in the wp-admin directory; and possibly (13) list directory contents of the wp-includes directory.  NOTE: the vars.php, edit-form.php, wp-settings.php, and edit-form-comment.php vectors are already covered by CVE-2005-4463.  The menu-header.php vector is already covered by CVE-2005-2110.  Other vectors might be covered by CVE-2005-1688.  NOTE: if the typical installation of WordPress does not list any site-specific files to wp-includes, then vector [13] is not an exposure.

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

It affects 1 product.


Products: Wordpress Wordpress.

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

Upgrade to a fixed version.

## Is CVE-2006-0986 being exploited?

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

## Other vulnerabilities in Wordpress Wordpress

- [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild)
- [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild)
- [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild)
- [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0986 is a medium-severity vulnerability in Wordpress Wordpress, published on 3 Mar 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-0986 in the wild and no public exploit code.

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

## Sources

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

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