dbcve.org
ElabftwApplication

CVE-2024-47826

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-14
Fix available
A fix is available. Upgrade to 5.1.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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. A vulnerability in versions prior to 5.1.5 allows an attacker to inject arbitrary HTML tags in the pages: "experiments.php" (show mode), "database.php" (show mode) or "search.php". It works by providing HTML code in the extended search string, which will then be displayed back to the user in the error message. This means that injected HTML will appear in a red "alert/danger" box, and be part of an error message. Due to some other security measures, it is not possible to execute arbitrary javascript from this attack. As such, this attack is deemed low impact. Users should upgrade to at least version 5.1.5 to receive a patch. No known workarounds are available.

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

A stored HTML injection vulnerability in eLabFTW versions before 5.1.5 allows attackers to inject arbitrary HTML tags through the extended search parameter on experiments.php, database.php, and search.php. The injected HTML is reflected back in an error message displayed in a red alert/danger box. While JavaScript execution is blocked by other security measures, the vulnerability still allows HTML injection.

MitigationUpgrade to eLabFTW version 5.1.5 or later to receive the patch. No workarounds are available.

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:< 5.1.5

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify eLabFTW installation
    Locate the eLabFTW installation directory or check running web services for eLabFTW. Look for experiments.php, database.php, or search.php files in the web root.
    Affected if eLabFTW is present in the environment
  2. Determine installed eLabFTW version
    Check the version number by viewing the changelog, version file, or the footer of the eLabFTW web interface. Compare against the affected range: versions before 5.1.5.
    Affected if The installed version is lower than 5.1.5
  3. Verify extended search feature access
    Confirm access to the extended search functionality on experiments.php, database.php, or search.php pages. These are the entry points for the vulnerable parameter.
    Affected if The extended search pages are accessible to authenticated users
  4. Confirm vulnerability condition
    The vulnerability triggers when the extended search parameter receives input that causes an error, reflecting back in a red alert/danger box. Check if error messages with user-supplied content are displayed.
    Affected if User input in the extended search is reflected in error messages without proper sanitization

A user is affected if eLabFTW version lower than 5.1.5 is installed and the extended search feature on experiments.php, database.php, or search.php is accessible.

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.5 or later
Fixed in 5.1.5
Interim mitigation

Upgrade to eLabFTW version 5.1.5 or later to receive the patch. No workarounds are available.

Recommended fix High confidence

5.1.5

  1. Upgrade ElabFTW to version 5.1.5 or later
  2. Consult the official ElabFTW upgrade documentation for your specific installation method (e.g., Docker, manual installation, or package manager)
  3. After upgrading, verify the fix by testing the extended search functionality on experiments.php, database.php, and search.php with HTML input to confirm the vulnerability is patched

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

Fix this in Elabftw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47826 — 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-47826 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