Teampass Cross-site Scripting

Teampass 2.1.26 allows reflected XSS via the index.php PATH_INFO. (2022-03-28, CVE-2022-26980)

TeamPass 2.1.27.36 allows Stored XSS at the Search page by setting a crafted password for an item in any folder. (2019-10-05, CVE-2019-17203)

TeamPass 2.1.27.36 allows Stored XSS by placing a payload in the username field during a login attempt. When an administrator looks at the log of failed logins, the XSS payload will be executed. (2019-10-05, CVE-2019-17205)

TeamPass 2.1.27.36 allows Stored XSS by setting a crafted Knowledge Base label and adding any available item. (2019-10-05, CVE-2019-17204)

TeamPass 2.1.27.36 allows Stored XSS by setting a crafted password for an item in a common available folder or sharing the item with an admin. (The crafted password is exploitable when viewing the change history of the item or tapping on the item.) (2019-09-26, CVE-2019-16904)

An issue was discovered in TeamPass 2.1.27.35. From the sources/items.queries.php "Import items" feature, it is possible to load a crafted CSV file with an XSS payload. (2019-08-06, CVE-2019-12950)

Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.

The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:

https://server.com/confirmation?message=Transaction+Complete

what results in:

<span>Confirmation: Transaction Complete</span>

In that case the message can be modified to become a valid Javascript code, e.g.:

https://server.com/confirmation?message=<script>dangerous javascript code here</script>

and it will be executed locally by the user's browser with full access to the user's personal application/browser data:

<span>Confirmation: <script>dangerous javascript code here</script></span>