Unauthenticated login via anonymous LDAP bind
Published Nov 20, 2024 · Updated Feb 23, 2026
Authentication bypass in M-Files Server before 24.11 allows remote attackers to log in without a password through LDAP. The LDAP authentication path treats a successful anonymous bind as proof of user authentication instead of rejecting a missing password. Exploitation requires LDAP authentication and an OpenLDAP server configured to permit anonymous binding, which is not enabled by default.
Summary
What happened
Authentication bypass in M-Files Server before 24.11 allows remote attackers to log in without a password through LDAP. The LDAP authentication path treats a successful anonymous bind as proof of user authentication instead of rejecting a missing password. Exploitation requires LDAP authentication and an OpenLDAP server configured to permit anonymous binding, which is not enabled by default.
The record
- CVE
- CVE-2024-10127
- Published
- Nov 20, 2024
- Updated
- Feb 23, 2026
- Vendor
- M-Files
- Product
- M-Files
- Classifications
- CWE-303
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 20, 2024CVE publishedPublication date reported by the CVE source.
- Feb 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <24.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo