dbcve.org
ElabftwApplication

CVE-2024-25632

HIGH · 8.8 CVSS v3.1 Published 2024-10-01
Fix available
A fix is available. Upgrade to 5.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a privilege escalation vulnerability in eLabFTW electronic lab notebook software. The flaw allows a regular team member to elevate their privileges to team administrator within teams they belong to. In versions after v5.0.0, an unauthenticated attacker can potentially gain administrative privileges over arbitrary teams through insecure handling of user registration or team creation mechanisms. The vulnerability stems from broken access control in the team administration privilege assignment.

MitigationUpgrade to eLabFTW version 5.1.0. Alternatively, if immediate upgrade is not possible, disable local user registration, disable saml_team_create setting, and restrict administrators from importing users into teams.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElabftwApplication
Affected:>= 4.6.0, < 5.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed eLabFTW version
    Locate the version number through the web interface (typically in the footer or About page) or check the installed package/version file in the eLabFTW installation directory
    Affected if The installed version is 4.6.0 or higher but lower than 5.1.0
  2. Verify if local user registration is enabled
    Check the eLabFTW configuration settings for any option that controls local/user-based account creation or self-registration
    Affected if Local user registration is enabled and the installed version is in the affected range
  3. Verify if saml_team_create functionality is accessible
    Check the SAML configuration or team creation settings for any feature allowing team creation via SAML identity provider
    Affected if The saml_team_create feature is enabled or accessible and the installed version is after v5.0.0
  4. Verify if user import functionality is accessible
    Check for any admin-imported user functionality or bulk user creation feature in the configuration or admin panel
    Affected if User import capabilities are available and the installed version is after v5.0.0

You are affected if your eLabFTW installation version is 4.6.0 or higher but lower than 5.1.0, and any of the following are true: local user registration is enabled, saml_team_create is accessible, or user import functionality is available (especially in versions after 5.0.0 where unauthenticated exploitation is possible).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.1.0 or later
Fixed in 5.1.0
Interim mitigation

Upgrade to eLabFTW version 5.1.0. Alternatively, if immediate upgrade is not possible, disable local user registration, disable saml_team_create setting, and restrict administrators from importing users into teams.

Recommended fix High confidence

5.1.0

  1. 1. Back up your eLabFTW installation and database before upgrading.
  2. 2. Upgrade eLabFTW to version 5.1.0 or later following the official upgrade documentation.
  3. 3. As additional hardening, configure the following in your settings: set 'Allow local registration' to disabled, set 'saml_team_create' to disabled, and restrict administrators from importing users into teams.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Elabftw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25632 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data