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

> Remote attackers can inject arbitrary web script or HTML into Mantis bug tracker, potentially compromising user sessions or data.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-57hc-wp4j-p6hv

## What is CVE-2006-0664?

CVE-2006-0664 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Feb 2006. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in config_defaults_inc.php in Mantis before 1.0 allows remote attackers to inject arbitrary web script or HTML via unknown attack vectors.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.  An original vendor bug report is referenced, but not accessible to the general public.

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

It affects 1 product.


Products: Mantis Mantis.

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

Upgrade to a fixed version.

## Is CVE-2006-0664 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6515](https://insights.sbomify.com/CVE-2006-6515/): Missing authorization in n/a (critical 10.0)
- [CVE-2006-0665](https://insights.sbomify.com/CVE-2006-0665/): Other in n/a (critical 10.0)
- [CVE-2002-1110](https://insights.sbomify.com/CVE-2002-1110/): SQL injection in n/a (critical 10.0)
- [CVE-2008-4687](https://insights.sbomify.com/CVE-2008-4687/): Code injection in n/a (critical 9.0)
- [CVE-2008-4689](https://insights.sbomify.com/CVE-2008-4689/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0664 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Feb 2006. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-0664 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-0664/ (Markdown: https://insights.sbomify.com/CVE-2006-0664/index.md)
```

## Sources

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

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