# CVE-2012-1892: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into Microsoft Visual Studio Team Foundation Server via an unspecified parameter.

- **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:** No
- **Published:** 11 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7q5p-6568-pm3p

## What is CVE-2012-1892?

CVE-2012-1892 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Sep 2012. 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 Microsoft Visual Studio Team Foundation Server 2010 SP1 allows remote attackers to inject arbitrary web script or HTML via an unspecified parameter, aka "XSS Vulnerability."

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

## Which versions are affected by CVE-2012-1892?

It affects 1 product.


Products: Microsoft Visual Studio Team Foundation Server.

## How do I fix CVE-2012-1892?

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

## Is CVE-2012-1892 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1892 and fix it if it is affected.

What it is: CVE-2012-1892 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Sep 2012. 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-2012-1892 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-2012-1892/ (Markdown: https://insights.sbomify.com/CVE-2012-1892/index.md)
```

## Sources

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

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