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

> Remote attackers can obtain sensitive path information via direct requests to specific PHP files in Grayscale BandSite CMS.

- **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:** No
- **Published:** 26 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m3wh-gq64-cmvh

## What is CVE-2006-4986?

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

### Official description

Grayscale BandSite CMS allows remote attackers to obtain sensitive information via a direct request for (1) certain files in the includes/content directory, (2) includes/shows_preview.php, and (3) adminpanel/configform.php; and files in adminpanel/includes/ including (4) mailinglist/disphtmltbl.php, (5) mailinglist/dispxls.php, (6) mailinglist/sendshows.php, (7) previews/preview_bio.php, (8) previews/preview_genmerch.php, (9) previews/preview_fliers.php, (10) previews/preview_gbook.php, (11) previews/preview_interviews.php, (12) previews/preview_links.php, (13) previews/preview_lyrics.php, (14) previews/preview_membio.php, (15) previews/preview_merchphotos.php, (16) previews/preview_mp3s.php, (17) previews/preview_news.php, (18) previews/preview_photos.php, (19) previews/preview_releases.php, (20) previews/preview_relmerch.php, (21) previews/preview_relphotos.php, (22) previews/preview_reviews.php, (23) previews/preview_shows.php, (24) previews/preview_wearmerch.php, (25) change_forms/change_bio.php, (26) change_forms/change_fliers.php, (27) change_forms/change_gbook.php, (28) change_forms/change_gen_merch.php, (29) change_forms/change_interview.php, (30) change_forms/change_links.php, (31) change_forms/change_lyrics.php, (32) change_forms/change_members.php, (33) change_forms/change_merch.php, (34) change_forms/change_merch_pic.php, (35) change_forms/change_mp3s.php, (36) change_forms/change_news.php, (37) change_forms/change_photos.php, (38) change_forms/change_rel_merch.php, (39) change_forms/change_rel_pic.php, (40) change_forms/change_releases.php, (41) change_forms/change_reviews.php, (42) change_forms/change_shows.php, and (43) change_forms/change_wear_merch.php, which reveals the path in various error messages.

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

It affects 1 product.


Products: Grayscale Bandsite Cms.

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

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

## Is CVE-2006-4986 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4984](https://insights.sbomify.com/CVE-2006-4984/): Code injection in n/a (high 7.5)
- [CVE-2006-3193](https://insights.sbomify.com/CVE-2006-3193/): Code injection in n/a (medium 5.1)
- [CVE-2006-4985](https://insights.sbomify.com/CVE-2006-4985/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4986 is a medium-severity vulnerability in n/a, published on 26 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-4986 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-4986/ (Markdown: https://insights.sbomify.com/CVE-2006-4986/index.md)
```

## Sources

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

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