CVE-2024-28100
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 · uneditedeLabFTW is an open source electronic lab notebook for research labs. By uploading specially crafted files, a regular user can create a circumstance where a visitor's browser runs arbitrary JavaScript code in the context of the eLabFTW application. This can be triggered by the visitor viewing a list of experiments. Viewing this allows the malicious script to act on behalf of the visitor in any way, including the creation of API keys for persistence, or other options normally available to the user. If the user viewing the page has the sysadmin role in eLabFTW, the script can act as a sysadmin (including system configuration and extensive user management roles). Users are advised to upgrade to at least version 5.0.0. There are no known workarounds for this vulnerability.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in eLabFTW where a regular authenticated user can upload specially crafted files containing malicious JavaScript. When other users (including visitors) view a list of experiments containing these files, the embedded script executes in their browser context, allowing the attacker to perform actions on behalf of the victim user, including creating API keys for persistence.
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< 5.0.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check eLabFTW versionAccess the admin panel or check the version file/version endpoint. In Docker deployments, run 'docker exec <container> cat version.txt' or check the image tag. The version is typically displayed in the footer of the eLabFTW interface.Affected if The installed version is lower than 5.0.0 (e.g., 4.x.x series)
-
Verify file upload is enabled for usersLog in as an administrator, navigate to the configuration or security settings panel, and check if the file upload feature is permitted for regular authenticated users.Affected if File uploads are enabled for non-admin users, allowing them to attach files to experiments
-
Inspect uploaded files in experimentsBrowse through experiment listings, particularly those created by regular users, and examine any attached files for suspicious file extensions or unexpected MIME types.Affected if There are uploaded files present in experiments that could contain embedded scripts
-
Review recent experiment activity for malicious filesCheck server logs or the database for recent file uploads with potentially executable content (.html, .js, .svg files uploaded as other types).Affected if Non-image/document files were recently uploaded to experiments
You are affected if your eLabFTW installation is version 4.x or lower AND allows regular users to upload files to experiments.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.0.0
Upgrade eLabFTW to version 5.0.0 or later to remediate this vulnerability. No workarounds are available.
5.0.0
- Backup your current eLabFTW installation and database before upgrading
- Review the eLabFTW 5.0.0 release notes for any specific upgrade instructions
- Upgrade eLabFTW to version 5.0.0 or later
- Verify the upgrade was successful by logging in
- Test that file uploads work correctly and that XSS payloads in filenames are no longer executed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28100 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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