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

> Remote attackers can inject arbitrary web script or HTML into the IPAM web interface via the search field, 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:** 31 Oct 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fcrw-2r23-93jj

## What is CVE-2012-4939?

CVE-2012-4939 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 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 IPAMSummaryView.aspx in the IPAM web interface before 3.0-HotFix1 in SolarWinds Orion Network Performance Monitor might allow remote attackers to inject arbitrary web script or HTML via the "Search for an IP address" field.

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

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

It affects 2 products.


Products: Solarwinds Ip Address Manager Web Interface, Solarwinds Orion Network Performance Monitor.

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

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

## Is CVE-2012-4939 being exploited?

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

Public exploit code:

- SolarWinds Orion IP Address Manager (IPAM) - 'search.aspx' Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4939 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 2012. It can be exploited 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-2012-4939 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-2012-4939/ (Markdown: https://insights.sbomify.com/CVE-2012-4939/index.md)
```

## Sources

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

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