# CVE-2018-7603: Search Autocomplete

> An attacker can inject malicious scripts via autocomplete items in the Drupal Search Autocomplete module, potentially executing code in victim browsers.

- **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:** No
- **Published:** 15 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jhjp-3hp8-fjch

## What is CVE-2018-7603?

CVE-2018-7603 is a medium-severity cross-site scripting vulnerability in Drupal 3rd party module - Search Autocomplete, published on 15 Jan 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

In Drupal's 3rd party module search auto complete prior to versions 7.x-4.8 there is a Cross Site Scripting vulnerability. This Search Autocomplete module enables you to autocomplete textfield using data from your website (nodes, comments, etc.). The module doesn't sufficiently filter user-entered text among the autocompletion items leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability can be exploited by any user allowed to create one of the autocompletion item, for instance, nodes, users, comments.

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

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

It affects 1 product.


Products: Search Autocomplete Project Search Autocomplete.

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

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

## Is CVE-2018-7603 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7603 is a medium-severity cross-site scripting vulnerability in Drupal 3rd party module - Search Autocomplete, published on 15 Jan 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-7603 in the wild and no public exploit code.

Affected product: Drupal 3rd party module - Search Autocomplete. 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-7603/ (Markdown: https://insights.sbomify.com/CVE-2018-7603/index.md)
```

## Sources

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

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