NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

Passbolt API Stored XSS on first/last name during setupGHSA-2f46-4xjm-73x5

HIGHFix: passbolt/passbolt_api@6135b48

GHSA-2f46-4xjm-73x5 is a high-severity (CVSS 7.2) vulnerability in passbolt/passbolt_api. A fix is available for passbolt/passbolt_api — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Dec 5, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘passbolt/passbolt_api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistpassbolt/passbolt_apiall versions2.11.0composer require passbolt/passbolt_api:^2.11.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passbolt/passbolt_api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update passbolt/passbolt_api to 2.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2f46-4xjm-73x5 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### 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 visibl
O3 Security · Impact-Aware SCA

Is GHSA-2f46-4xjm-73x5 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Passbolt API Stored XSS on first/last name during setup