{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-39925 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-39925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-39925 is a medium-severity vulnerability in n/a, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-39925 and fix it if it is affected.\n\nWhat it is: CVE-2024-39925 is a medium-severity vulnerability in n/a, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-39925 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2024-39925/ (Markdown: https://insights.sbomify.com/CVE-2024-39925/index.md)","id":"CVE-2024-39925","markdown":"https://insights.sbomify.com/CVE-2024-39925/index.md","name":"CVE-2024-39925","record":{"aliases":["GHSA-r89w-9fr4-c7c9"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Password manager server","requires_auth":"low_privilege","summary":"An authenticated user can access encrypted organization data if they possess the organization key, which is not rotated upon member removal.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vaultwarden","vendor":"dani-garcia"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in Vaultwarden (formerly Bitwarden_RS) 1.30.3. It lacks an offboarding process for members who leave an organization. As a result, the shared organization key is not rotated when a member departs. Consequently, the departing member, whose access should be revoked, retains a copy of the organization key. Additionally, the application fails to adequately protect some encrypted data stored on the server. Consequently, an authenticated user could gain unauthorized access to encrypted data of any organization, even if the user is not a member of the targeted organization. However, the user would need to know the corresponding organizationId. Hence, if a user (whose access to an organization has been revoked) already possesses the organization key, that user could use the key to decrypt the leaked data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2024-39925","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-39926"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2024-39924"},"products":["n/a"],"published":"2024-09-13","related":[{"cvss_score":9.8,"headline":"Vaultwarden vulnerable to user impersonation","id":"CVE-2024-55225","kev_date_added":null,"published":"2025-01-09"},{"cvss_score":9.6,"headline":"Vaultwarden HTML injection vulnerability","id":"CVE-2024-55224","kev_date_added":null,"published":"2025-01-09"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-39924","kev_date_added":null,"published":"2024-09-13"},{"cvss_score":8.7,"headline":"Vaultwarden: Cross-Org Group Binding Enables Unauthorized Read And Write Access Into Another Organization","id":"CVE-2026-43912","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":8.3,"headline":"Vaultwarden: Privilege Escalation via Bulk Permission Update to Unauthorized Collections by Manager","id":"CVE-2026-27802","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.3,"headline":"Vaultwarden: Collection Management Operations Allowed Without `manage` Verification for Manager Role","id":"CVE-2026-27803","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.1,"headline":"Vaultwarden: Unconfirmed Owner Can Purge Entire Organization Vault","id":"CVE-2026-43913","kev_date_added":null,"published":"2026-05-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-22","vendors":["n/a"]},"summary":"An authenticated user can access encrypted organization data if they possess the organization key, which is not rotated upon member removal.","url":"https://insights.sbomify.com/CVE-2024-39925/"}