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

> Attackers can inject malicious scripts via profile fields or search bars in ServiceNow ITSM, potentially leading to session hijacking or code execution.

- **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:** 15 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pmrw-379c-rjhc

## What is CVE-2018-8720?

CVE-2018-8720 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Mar 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ServiceNow ITSM 2016-06-02 has XSS via the First Name or Last Name field of My Profile (aka navpage.do), or the Search bar of My Portal (aka search_results.do).

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

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

It affects 1 product.


Products: Servicenow It Service Management.

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

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

## Is CVE-2018-8720 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20768](https://insights.sbomify.com/CVE-2019-20768/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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