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

> An admin can execute cross-site scripting attacks via a modified URL in OTRS, potentially compromising user sessions or data.

- **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:** Yes
- **Published:** 11 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-19142, GHSA-644h-4r83-2cf3, UBUNTU-CVE-2018-19142

## What is CVE-2018-19142?

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

### Official description

Open Ticket Request System (OTRS) 6.0.x before 6.0.13 allows an admin to conduct an XSS attack via a modified URL.

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

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

It affects 1 product.


Products: Otrs Open Ticket Request System.

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

Upgrade to a fixed version.

## Is CVE-2018-19142 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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