# CVE-2020-15307: Cross-site scripting in n/a

> Attackers can inject malicious scripts via crafted custom field names in the Nozomi Guardian web interface, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 30 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pv98-x799-gjp6

## What is CVE-2020-15307?

CVE-2020-15307 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Jun 2020. 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

Nozomi Guardian before 19.0.4 allows attackers to achieve stored XSS (in the web front end) by leveraging the ability to create a custom field with a crafted field name.

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

## Which versions are affected by CVE-2020-15307?

It affects 1 product.


Products: Nozominetworks Guardian.

## How do I fix CVE-2020-15307?

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

## Is CVE-2020-15307 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-7049](https://insights.sbomify.com/CVE-2020-7049/): Other in n/a (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15307 and fix it if it is affected.

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

## Sources

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

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