🛡️ GHSA-2f46-4xjm-73x5 — passbolt-api

Passbolt API Stored XSS on first/last name during setup

Description

An administrator can craft a user with a malicious first name and last name, using a payload such as

```

<svg onload="confirm(document.domain)">'); ?></svg>

```

The user will then receive the invitation email and click on the setup link. The setup start page served by the server will fire the XSS.

Impact of issue

An administrator could use this exploit to edit the setup start page for a given user, for example, trick the user into installing another extension. Even though the severity of this issue in itself is high, the likelihood is low because the exploit will be visible in clear by the user in the email notification, and also requires an action from a malicious administrator.

Fix

Sanitize the firstname and lastname in the page that is used to trigger the extension setup process.

Additionally since v2.11 some default CSP are inserted in the server response headers to prevent inline-scripts or 3rd party domain scripts on pages served by the passbolt API. This is to cater for the case where the administrator has not set them up as part of the web server configuration.