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

> An attacker can execute arbitrary scripts in the victim's browser via a crafted URL in FreeBSD CVSweb, potentially affecting other sites on the same domain.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** Yes
- **Published:** 4 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1000998, GHSA-mxq7-h42w-wh9g

## What is CVE-2018-1000998?

CVE-2018-1000998 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2019. 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

FreeBSD CVSweb version 2.x contains a Cross Site Scripting (XSS) vulnerability in all pages that can result in limited impact--CVSweb is anonymous & read-only. It might impact other sites on same domain. This attack appears to be exploitable via victim must load specially crafted url. This vulnerability appears to have been fixed in 3.x.

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

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

It affects 1 product.


Products: Freebsd Cvsweb.

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

Upgrade to a fixed version.

## Is CVE-2018-1000998 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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