# CVE-2018-1441: Cross-site scripting in Monitoring

> Cross-site scripting in IBM Monitoring allows attackers to inject JavaScript, potentially stealing credentials from trusted sessions.

- **Severity:** Medium 6.1 (`CVSS:3.0/A:N/AC:L/AV:N/C:L/I:L/PR:N/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wv3h-3whc-x8xq

## What is CVE-2018-1441?

CVE-2018-1441 is a medium-severity cross-site scripting vulnerability in IBM Monitoring, published on 14 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

IBM Application Performance Management - Response Time Monitoring Agent (IBM Monitoring 8.1.3 and 8.1.4) 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. IBM X-Force ID: 139597.

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

## Which versions are affected by CVE-2018-1441?

It affects 1 product.


Products: Ibm Monitoring.

## How do I fix CVE-2018-1441?

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

## Is CVE-2018-1441 being exploited?

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

## Other vulnerabilities in IBM Monitoring

- [CVE-2018-1442](https://insights.sbomify.com/CVE-2018-1442/): Cross-site request forgery in Monitoring (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1441 and fix it if it is affected.

What it is: CVE-2018-1441 is a medium-severity cross-site scripting vulnerability in IBM Monitoring, published on 14 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1441 in the wild and no public exploit code.

Affected product: IBM Monitoring. 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-2018-1441/ (Markdown: https://insights.sbomify.com/CVE-2018-1441/index.md)
```

## Sources

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

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