# CVE-2017-15051: TeamPass stored cross-site scripting (XSS) vulnerability

> Authenticated attackers can inject malicious scripts via item URLs or profile logs, potentially compromising administrator sessions in TeamPass.

- **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:** Yes
- **Published:** 27 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r68m-4v39-cf43

## What is CVE-2017-15051?

CVE-2017-15051 is a medium-severity cross-site scripting vulnerability in Teampass Teampass, published on 27 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple stored cross-site scripting (XSS) vulnerabilities in TeamPass before 2.1.27.9 allow authenticated remote attackers to inject arbitrary web script or HTML via the (1) URL value of an item or (2) user log history. To exploit the vulnerability, the attacker must be first authenticated to the application. For the first one, the attacker has to simply inject XSS code within the URL field of a shared item. For the second one however, the attacker must prepare a payload within its profile, and then ask an administrator to modify its profile. From there, whenever the administrator accesses the log, it can be XSS'ed.

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

## Which versions are affected by CVE-2017-15051?

2 open source packages ship an affected version, including nilsteampassnet/teampass. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nilsteampassnet/teampass` | Packagist | All versions | 2.1.27.9 |
| `nilsteampassnet/teampass` | Packagist | All versions | 2.1.27.9 |

Products: Teampass Teampass.

## How do I fix CVE-2017-15051?

Upgrade nilsteampassnet/teampass to 2.1.27.9 or later.

## Is CVE-2017-15051 being exploited?

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

## Other vulnerabilities in Teampass Teampass

- [CVE-2019-1000001](https://insights.sbomify.com/CVE-2019-1000001/): TeamPass Storing Passwords in a Recoverable Format vulnerability (critical 9.8)
- [CVE-2017-9436](https://insights.sbomify.com/CVE-2017-9436/): TeamPass SQL injection in users.queries.php (critical 9.8)
- [CVE-2015-7564](https://insights.sbomify.com/CVE-2015-7564/): TeamPass vulnerable to SQL Injection (critical 9.8)
- [CVE-2026-3106](https://insights.sbomify.com/CVE-2026-3106/): Multiple vulnerabilities in Teampass (critical 9.3)
- [CVE-2026-3107](https://insights.sbomify.com/CVE-2026-3107/): Multiple vulnerabilities in Teampass (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15051 and fix it if it is affected.

What it is: CVE-2017-15051 is a medium-severity cross-site scripting vulnerability in Teampass Teampass, published on 27 Nov 2017. 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-2017-15051 in the wild and no public exploit code.

Affected packages and fixed versions:
- nilsteampassnet/teampass (Packagist): affected all versions; fixed in 2.1.27.9
- nilsteampassnet/teampass (Packagist): affected all versions; fixed in 2.1.27.9

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

## Sources

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

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