# CVE-2010-1557: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into HP Insight Control Server Migration, potentially compromising user sessions.

- **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:** 14 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gmgx-586c-27pm

## What is CVE-2010-1557?

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

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in HP Insight Control Server Migration before 6.0 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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

## Which versions are affected by CVE-2010-1557?

It affects 1 product.


Products: Hp Insight Control Server Migration for Windows.

## How do I fix CVE-2010-1557?

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

## Is CVE-2010-1557 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1557 and fix it if it is affected.

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

## Sources

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

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