eLabFTW up to 5.4.1 Multi-Factor Authentication authentication bypass by assumed-immutable data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in eLabFTW up to 5.4.1 and classified as problematic. This issue affects some unknown processing of the component Multi-Factor Authentication. This manipulation causes authentication bypass by assumed-immutable data. The identification of this vulnerability is CVE-2026-28510. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in eLabFTW up to 5.4.1. Affected by this vulnerability is an unknown part of the component Multi-Factor Authentication. The manipulation with an unknown input leads to a authentication bypass by assumed-immutable data vulnerability. The CWE definition for the vulnerability is CWE-302. The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
eLabFTW is an open source electronic lab notebook. In elabftw versions through 5.4.1, the login flow did not reliably preserve the multi-factor authentication state across authentication steps. Under certain conditions, an attacker with valid primary credentials could complete authentication with an attacker-controlled TOTP secret and bypass the additional factor. This could result in unauthorized account access. This issue is fixed in version 5.4.2.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-28510 since 02/27/2026. The exploitation appears to be difficult. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 5.4.2 eliminates this vulnerability. Applying the patch 8b7a575aef128870861187eaa2b2f0f08654ecf9 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
- Product: https://github.com/elabftw/elabftw/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Authentication bypass by assumed-immutable dataCWE: CWE-302
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: eLabFTW 5.4.2
Patch: 8b7a575aef128870861187eaa2b2f0f08654ecf9
Timeline
02/27/2026 CVE reserved05/05/2026 Advisory disclosed
05/05/2026 VulDB entry created
05/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-x5wv-c9q4-fj65
Status: Confirmed
CVE: CVE-2026-28510 (🔒)
GCVE (CVE): GCVE-0-2026-28510
GCVE (VulDB): GCVE-100-361189
Entry
Created: 05/05/2026 19:01Changes: 05/05/2026 19:01 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.