# CVE-2006-4985: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into Grayscale BandSite CMS via multiple parameters, potentially leading to session hijacking or data theft.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7qv9-7c8f-pg23

## What is CVE-2006-4985?

CVE-2006-4985 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Sep 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Grayscale BandSite CMS allow remote attackers to inject arbitrary web script or HTML via (1) the max_file_size_purdy parameter in adminpanel/includes/helpfiles/help_mp3.php, (2) the message_text parameter in adminpanel/includes/mailinglist/sendemail.php, (3) the this_year parameter in includes/footer.php, and the band parameter in (4) adminpanel/includes/helpfiles/help_news.php (5) adminpanel/includes/helpfiles/help_merch.php, (6) adminpanel/includes/header.php, and (7) adminpanel/login_header.php; and includes/content/ files including (8) bio_content.php, (9) gbook_content.php, (10) interview_content.php, (11) links_content.php, (12) lyrics_content.php, (13) member_content.php, (14) merch_content.php, (15) mp3_content.php, (16) news_content.php, (17) pastshows_content.php, (18) photo_content.php, (19) releases_content.php, (20) reviews_content.php, (21) shows_content.php, and (22) signgbook_content.php.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Grayscale Bandsite Cms.

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

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

## Is CVE-2006-4985 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4985 exists.

Public exploit code:

- BandSite CMS 1.1 - 'help_news.php' Cross-Site Scripting (exploitdb)
- BandSite CMS 1.1 - 'help_merch.php' Cross-Site Scripting (exploitdb)
- BandSite CMS 1.1 - 'help_mp3.php' Cross-Site Scripting (exploitdb)
- BandSite CMS 1.1 - 'sendemail.php' Cross-Site Scripting (exploitdb)
- BandSite CMS 1.1 - 'header.php' Cross-Site Scripting (exploitdb)
- BandSite CMS 1.1 - 'login_header.php' Cross-Site Scripting (exploitdb)

## 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-4986](https://insights.sbomify.com/CVE-2006-4986/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4985 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Sep 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4985 exists.

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

## Sources

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

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