# CVE-2018-15528: Cross-site scripting in n/a

> A remote attacker can inject client-side scripts into the BMC MyIT SSO plugin via a crafted link, potentially executing arbitrary code in the victim's browser.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 21 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mvqc-qf5q-pvwc

## What is CVE-2018-15528?

CVE-2018-15528 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Aug 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

Reflected Cross-Site Scripting exists in the Java System Solutions SSO plugin 4.0.13.1 for BMC MyIT. A remote attacker can abuse this issue to inject client-side scripts into the "select_sso()" function. The payload is triggered when the victim opens a prepared /ux/jss-sso/arslogin?[XSS] link and then clicks the "Login" button.

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

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

It affects 1 product.


Products: Javasystemsolutions Sso Plugin.

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

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

## Is CVE-2018-15528 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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