{"answers":{"affected":"2 open source packages ship an affected version, including passbolt/passbolt_api.","exploited":"There is no known exploitation of GHSA-2f46-4xjm-73x5 in the wild and no public exploit code.","fix":"Upgrade passbolt/passbolt_api to 2.11.0 or later.","what":"GHSA-2f46-4xjm-73x5 is a cross-site scripting vulnerability in passbolt/passbolt_api, published on 20 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-2f46-4xjm-73x5 and fix it if it is affected.\n\nWhat it is: GHSA-2f46-4xjm-73x5 is a cross-site scripting vulnerability in passbolt/passbolt_api, published on 20 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-2f46-4xjm-73x5 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- passbolt/passbolt_api (Packagist): affected all versions; fixed in 2.11.0\n- passbolt/passbolt_api (Packagist): affected all versions; fixed in 2.11.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-2f46-4xjm-73x5/ (Markdown: https://insights.sbomify.com/GHSA-2f46-4xjm-73x5/index.md)","id":"GHSA-2f46-4xjm-73x5","markdown":"https://insights.sbomify.com/GHSA-2f46-4xjm-73x5/index.md","name":"GHSA-2f46-4xjm-73x5","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Passbolt API","requires_auth":"high_privilege","summary":"A malicious administrator can inject scripts into user setup pages via stored XSS in name fields, potentially tricking users into installing extensions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Description\nAn administrator can craft a user with a malicious first name and last name, using a payload such as\n```\n\u003csvg onload=\"confirm(document.domain)\"\u003e'); ?\u003e\u003c/svg\u003e\n```\nThe 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.\n\n### Impact of issue\nAn 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.\n\n### Fix\nSanitize the firstname and lastname in the page that is used to trigger the extension setup process.\n\nAdditionally 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.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Passbolt API Stored XSS on first/last name during setup","id":"GHSA-2f46-4xjm-73x5","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["2.11.0"],"introduced":["0"],"last_affected":[],"package":"passbolt/passbolt_api","purl":null,"source":"GHSA-2f46-4xjm-73x5"},{"ecosystem":"Packagist","fixed":["2.11.0"],"introduced":["0"],"last_affected":[],"package":"passbolt/passbolt_api","purl":"pkg:composer/passbolt/passbolt_api","source":"GHSA-2f46-4xjm-73x5"}],"products":null,"published":"2024-05-20","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious administrator can inject scripts into user setup pages via stored XSS in name fields, potentially tricking users into installing extensions.","url":"https://insights.sbomify.com/GHSA-2f46-4xjm-73x5/"}