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

> Reflected Cross-Site Scripting in OpenText Documentum D2 Webtop allows attackers to execute scripts via malicious parameters, potentially compromising user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fqmq-5wxp-jj3w

## What is CVE-2018-7660?

CVE-2018-7660 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In OpenText Documentum D2 Webtop v4.6.0030 build 059, a Reflected Cross-Site Scripting Vulnerability could potentially be exploited by malicious users to compromise the affected system via the servlet/Download _docbase or _username parameter.

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

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

It affects 1 product.


Products: Opentext Documentum D2.

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

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

## Is CVE-2018-7660 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5586](https://insights.sbomify.com/CVE-2017-5586/): Deserialization in n/a (critical 9.8)
- [CVE-2018-7659](https://insights.sbomify.com/CVE-2018-7659/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7660 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-7660 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-7660/ (Markdown: https://insights.sbomify.com/CVE-2018-7660/index.md)
```

## Sources

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

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