# CVE-2019-12863: Cross-site scripting in n/a

> Administrators can inject stored HTML into the Web Console Settings, potentially leading to code execution or account takeover.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q6rp-fxm7-mjq8

## What is CVE-2019-12863?

CVE-2019-12863 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Feb 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

SolarWinds Orion Platform 2018.4 HF3 (NPM 12.4, NetPath 1.1.4) allows Stored HTML Injection by administrators via the Web Console Settings screen.

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

## Which versions are affected by CVE-2019-12863?

It affects 3 products.


Products: Solarwinds Netpath, Solarwinds Network Performance Monitor, Solarwinds Orion Platform.

## How do I fix CVE-2019-12863?

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

## Is CVE-2019-12863 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12864](https://insights.sbomify.com/CVE-2019-12864/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12863 and fix it if it is affected.

What it is: CVE-2019-12863 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Feb 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-12863 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-2019-12863/ (Markdown: https://insights.sbomify.com/CVE-2019-12863/index.md)
```

## Sources

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

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