# CVE-2016-6072: Cross-site scripting in Maximo Asset Management

> Attackers can inject JavaScript into the IBM Maximo web interface to steal user credentials and alter functionality.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2gg4-ghg8-24r5

## What is CVE-2016-6072?

CVE-2016-6072 is a medium-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 1 Feb 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

IBM Maximo Asset Management is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

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

## Which versions are affected by CVE-2016-6072?

It affects 12 products.


Products: Ibm Maximo Asset Management, Ibm Maximo for Aviation, Ibm Maximo for Life Sciences, Ibm Maximo for Nuclear Power, Ibm Maximo for Oil and Gas, Ibm Maximo for Transportation, Ibm Maximo for Utilities, Ibm Smartcloud Control Desk, Ibm Tivoli Asset Management for It, Ibm Tivoli Change and Configuration Management Database, Ibm Tivoli Integration Composer, Ibm Tivoli Service Request Manager.

## How do I fix CVE-2016-6072?

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

## Is CVE-2016-6072 being exploited?

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

## Other vulnerabilities in Ibm Maximo Asset Management

- [CVE-2020-4493](https://insights.sbomify.com/CVE-2020-4493/): Auth bypass in Maximo Asset Management (critical 9.8)
- [CVE-2017-1175](https://insights.sbomify.com/CVE-2017-1175/): SQL injection in Maximo Asset Management (critical 9.8)
- [CVE-2020-4521](https://insights.sbomify.com/CVE-2020-4521/): Deserialization in Maximo Asset Management (high 8.8)
- [CVE-2018-1524](https://insights.sbomify.com/CVE-2018-1524/): Hardcoded credentials in Maximo Asset Management (high 8.8)
- [CVE-2018-1414](https://insights.sbomify.com/CVE-2018-1414/): SQL injection in Maximo Asset Management (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6072 and fix it if it is affected.

What it is: CVE-2016-6072 is a medium-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 1 Feb 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-6072 in the wild and no public exploit code.

Affected product: Ibm Maximo Asset Management. 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-2016-6072/ (Markdown: https://insights.sbomify.com/CVE-2016-6072/index.md)
```

## Sources

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

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