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

> Attackers can inject malicious scripts via query preference parameters, leading to code execution when users visit the index view.

- **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:** 9 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hcxx-xr69-wv56

## What is CVE-2018-1000029?

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

mcholste Enterprise Log Search and Archive (ELSA) version revision 1205, commit 2cc17f1 and earlier contains a Cross Site Scripting (XSS) vulnerability in index view (/) that can result in . This attack appear to be exploitable via Payload delivered via the type, name, and value parameters of /Query/set_preference and the name and value parameters of /Query/preference. Payload executed when the user visits the index view (/).

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

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

It affects 1 product.


Products: Elsa Project Elsa.

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

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

## Is CVE-2018-1000029 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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