# CVE-2015-6005: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple input fields in IPSwitch WhatsUp Gold, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rprf-x38f-c4gm

## What is CVE-2015-6005?

CVE-2015-6005 is a medium-severity cross-site scripting vulnerability in Progress Whatsup Gold, published on 27 Dec 2015. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in IPSwitch WhatsUp Gold before 16.4 allow remote attackers to inject arbitrary web script or HTML via (1) an SNMP OID object, (2) an SNMP trap message, (3) the View Names field, (4) the Group Names field, (5) the Flow Monitor Credentials field, (6) the Flow Monitor Threshold Name field, (7) the Task Library Name field, (8) the Task Library Description field, (9) the Policy Library Name field, (10) the Policy Library Description field, (11) the Template Library Name field, (12) the Template Library Description field, (13) the System Script Library Name field, (14) the System Script Library Description field, or (15) the CLI Settings Library Description field.

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

## Which versions are affected by CVE-2015-6005?

It affects 1 product.


Products: Progress Whatsup Gold.

## How do I fix CVE-2015-6005?

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

## Is CVE-2015-6005 being exploited?

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

## Other vulnerabilities in Progress Whatsup Gold

- [CVE-2024-6670](https://insights.sbomify.com/CVE-2024-6670/): Progress WhatsUp Gold SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2024-4885](https://insights.sbomify.com/CVE-2024-4885/): Progress WhatsUp Gold Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2024-46909](https://insights.sbomify.com/CVE-2024-46909/): WhatsUp Gold WriteDataFile Directory Traversal Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-8785](https://insights.sbomify.com/CVE-2024-8785/): WhatsUp Gold Registry Overwrite Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-7763](https://insights.sbomify.com/CVE-2024-7763/): WhatsUp Gold getReport Missing Authentication Authentication Bypass Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6005 and fix it if it is affected.

What it is: CVE-2015-6005 is a medium-severity cross-site scripting vulnerability in Progress Whatsup Gold, published on 27 Dec 2015. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-6005 in the wild and no public exploit code.

Affected product: Progress Whatsup Gold. 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-2015-6005/ (Markdown: https://insights.sbomify.com/CVE-2015-6005/index.md)
```

## Sources

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

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