# CVE-2018-1000516: Galaxy cross-site scripting (XSS)

> Attackers can execute arbitrary JavaScript in Galaxy users' browsers via unsanitized input in templates, potentially leading to account takeover.

- **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:** 26 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qqr6-vm23-m488, PYSEC-2018-149

## What is CVE-2018-1000516?

CVE-2018-1000516 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jun 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

The Galaxy Project Galaxy version v14.10 contains a CWE-79: Improper Neutralization of Input During Web Page Generation vulnerability in Many templates used in the Galaxy server did not properly sanitize user's input, which would allow for cross-site scripting (XSS) attacks. In this form of attack, a malicious person can create a URL which, when opened by a Galaxy user or administrator, would allow the malicious user to execute arbitrary Javascript. that can result in Arbitrary JavaScript code execution. This attack appear to be exploitable via The victim must interact with component on page witch contains injected JavaScript code.. This vulnerability appears to have been fixed in v14.10.1, v15.01.

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

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

5 open source packages ship an affected version, including galaxy-app. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `galaxy-app` | PyPI | All versions | 14.10.1, 15.01 |
| `galaxy-app` | PyPI | All versions | 14.10.1 |
| `galaxy-app` | PyPI | All versions | 14.10.1 |
| `galaxy-app` | PyPI | From 15.0 | 15.01 |
| `galaxy-app` | PyPI | From 15.0 | 15.01 |

Products: Galaxyproject Galaxy.

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

Upgrade galaxy-app to a fixed version for your release line: 14.10.1 or 15.01.

## Is CVE-2018-1000516 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27578](https://insights.sbomify.com/CVE-2023-27578/): Galaxy vulnerable to unauthorized modification of pages/visualizations due to insufficient permission check (critical 9.1)
- [CVE-2022-23470](https://insights.sbomify.com/CVE-2022-23470/): Arbitrary file access in the Galaxy data analysis platform (high 8.6)
- [CVE-2024-42346](https://insights.sbomify.com/CVE-2024-42346/): Stored Cross Site Scripting (Stored XSS) in Galaxy (high 7.6)
- [CVE-2024-42351](https://insights.sbomify.com/CVE-2024-42351/): Possible Data Tampering & Loss of Public Datasets in Galaxy (medium 6.5)
- [CVE-2023-42812](https://insights.sbomify.com/CVE-2023-42812/): Galaxy vulnerable to Server Side Request Forgery during data imports (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000516 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jun 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-1000516 in the wild and no public exploit code.

Affected packages and fixed versions:
- galaxy-app (PyPI): affected all versions; fixed in 14.10.1, 15.01
- galaxy-app (PyPI): affected all versions; fixed in 14.10.1
- galaxy-app (PyPI): affected all versions; fixed in 14.10.1
- galaxy-app (PyPI): affected from 15.0; fixed in 15.01
- galaxy-app (PyPI): affected from 15.0; fixed in 15.01

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-1000516/ (Markdown: https://insights.sbomify.com/CVE-2018-1000516/index.md)
```

## Sources

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

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