{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-25632 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-25632 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25632 is a high-severity vulnerability in elabftw, published on 1 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-25632 and fix it if it is affected.\n\nWhat it is: CVE-2024-25632 is a high-severity vulnerability in elabftw, published on 1 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-25632 in the wild and no public exploit code.\n\nAffected product: elabftw. 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-25632/ (Markdown: https://insights.sbomify.com/CVE-2024-25632/index.md)","id":"CVE-2024-25632","markdown":"https://insights.sbomify.com/CVE-2024-25632/index.md","name":"CVE-2024-25632","record":{"aliases":["GHSA-6m7p-gh9f-5mgg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Electronic lab notebook","requires_auth":"none","summary":"Attackers can gain administrator privileges over arbitrary teams in eLabFTW, potentially compromising team data and management.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"elabftw","vendor":"elabftw"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-842","name":"Placement of User into Incorrect Group"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"eLabFTW is an open source electronic lab notebook for research labs. In the context of eLabFTW, an administrator is a user account with certain privileges to manage users and content in their assigned team/teams. A user may be an administrator in one team and a regular user in another. The vulnerability allows a regular user to become administrator of a team where they are a member, under a reasonable configuration. Additionally, in eLabFTW versions subsequent to v5.0.0, the vulnerability may allow an initially unauthenticated user to gain administrative privileges over an arbitrary team. The vulnerability does not affect system administrator status. Users should upgrade to version 5.1.0. System administrators are advised to turn off local user registration, saml_team_create and not allow administrators to import users into teams, unless strictly required.","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":"Unauthorised granting of administrator privileges over arbitrary teams under certain circumstances","id":"CVE-2024-25632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"In eLabFTW, if administrators can create users, users can too","id":"CVE-2024-25633"},"packages":[],"prev":{"headline":"Unencrypted traffic between pods when using Wireguard and an external kvstore","id":"CVE-2024-25631"},"products":["elabftw"],"published":"2024-10-01","related":[{"cvss_score":9.1,"headline":"Incorrect Authentication in elabftw","id":"CVE-2021-43834","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":8.9,"headline":"Stored Cross-site Scripting leading to arbitrary actions taken on behalf of users in elabftw","id":"CVE-2024-28100","kev_date_added":null,"published":"2024-09-02"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2019-12185","kev_date_added":null,"published":"2019-05-19"},{"cvss_score":8.3,"headline":"Incorrect input validation could allow an authenticated user to read sensitive information","id":"CVE-2025-25206","kev_date_added":null,"published":"2025-02-14"},{"cvss_score":8.1,"headline":"Account takeover in eLabFTW","id":"CVE-2021-43833","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":7.5,"headline":"eLabFTW contains a direct and indirect information disclosure","id":"CVE-2024-45408","kev_date_added":null,"published":"2024-10-01"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-01","vendors":["elabftw"]},"summary":"Attackers can gain administrator privileges over arbitrary teams in eLabFTW, potentially compromising team data and management.","url":"https://insights.sbomify.com/CVE-2024-25632/"}