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

> Stored XSS in Zenitel IP-StationWeb allows attackers to steal admin credentials or hijack sessions via malicious display names.

- **Severity:** Medium 4.8 (`CVSS:3.0/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:** 6 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c7qj-g8mp-6q7h

## What is CVE-2018-19927?

CVE-2018-19927 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Dec 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Zenitel Norway IP-StationWeb before 4.2.3.9 allows stored XSS via the Display Name for Station Status or Account Settings, related to the goform/zForm_save_changes sip_nick parameter. The password of alphaadmin for the admin account may be used for authentication in some cases.

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

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

It affects 1 product.


Products: Zenitel Ip-Stationweb Firmware.

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

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

## Is CVE-2018-19927 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19926](https://insights.sbomify.com/CVE-2018-19926/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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