# CVE-2008-2776: Cross-site scripting (XSS) vulnerability in search.asp in DT Centrepiece 4.0 allows remote attackers to inject arbitrary web script or HTML


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3vcm-3w42-g672

## What is CVE-2008-2776?

CVE-2008-2776 is a medium-severity vulnerability in n/a, published on 19 Jun 2008. 

### Official description

Cross-site scripting (XSS) vulnerability in search.asp in DT Centrepiece 4.0 allows remote attackers to inject arbitrary web script or HTML via the searchFor parameter.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

## Which versions are affected by CVE-2008-2776?

It affects 1 product.


Products: Dt Centrepiece Dt Centrepiece.

## How do I fix CVE-2008-2776?

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

## Is CVE-2008-2776 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2775](https://insights.sbomify.com/CVE-2008-2775/): SQL injection vulnerability in search.asp in DT Centrepiece 4.0 allows remote attackers to execute arbitrary SQL commands via the searchFor parameter. (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2776 and fix it if it is affected.

What it is: CVE-2008-2776 is a medium-severity vulnerability in n/a, published on 19 Jun 2008. 
Exploitation: There is no known exploitation of CVE-2008-2776 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-2008-2776/ (Markdown: https://insights.sbomify.com/CVE-2008-2776/index.md)
```

## Sources

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

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