Mattermost up to 9.11.11/10.4.4/10.5.2/10.6.1 LDAP Lockout overly restrictive account lockout mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Mattermost up to 9.11.11/10.4.4/10.5.2/10.6.1. Impacted is an unknown function of the component LDAP Lockout. This manipulation causes overly restrictive account lockout mechanism. This vulnerability is handled as CVE-2025-31947. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Mattermost up to 9.11.11/10.4.4/10.5.2/10.6.1. Affected by this vulnerability is an unknown code of the component LDAP Lockout. The manipulation with an unknown input leads to a overly restrictive account lockout mechanism vulnerability. The CWE definition for the vulnerability is CWE-645. The product contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily, which allows attackers to deny service to legitimate users by causing their accounts to be locked out. As an impact it is known to affect availability. The summary by CVE is:
Mattermost versions 10.6.x <= 10.6.1, 10.5.x <= 10.5.2, 10.4.x <= 10.4.4, 9.11.x <= 9.11.11 fail to lockout LDAP users following repeated login failures, which allows attackers to lock external LDAP accounts through repeated login failures through Mattermost.
The weakness was released by John Landells. The advisory is shared at mattermost.com. This vulnerability is known as CVE-2025-31947 since 04/08/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
Upgrading to version 9.11.12, 10.4.5, 10.5.3, 10.6.2 or 10.7.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-15150). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 9.11.0
- 9.11.1
- 9.11.2
- 9.11.3
- 9.11.4
- 9.11.5
- 9.11.6
- 9.11.7
- 9.11.8
- 9.11.9
- 9.11.10
- 9.11.11
- 10.4.0
- 10.4.1
- 10.4.2
- 10.4.3
- 10.4.4
- 10.5.0
- 10.5.1
- 10.5.2
- 10.6.0
- 10.6.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔒
CNA Base Score: 5.8
CNA Vector (Mattermost): 🔒
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: Overly restrictive account lockout mechanismCWE: CWE-645 / CWE-404
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: Mattermost 9.11.12/10.4.5/10.5.3/10.6.2/10.7.0
Timeline
04/08/2025 CVE reserved05/15/2025 Advisory disclosed
05/15/2025 VulDB entry created
10/07/2025 VulDB entry last update
Sources
Advisory: mattermost.comResearcher: John Landells
Status: Confirmed
CVE: CVE-2025-31947 (🔒)
GCVE (CVE): GCVE-0-2025-31947
GCVE (VulDB): GCVE-100-309061
EUVD: 🔒
Entry
Created: 05/15/2025 13:42Updated: 10/07/2025 04:02
Changes: 05/15/2025 13:42 (64), 05/15/2025 15:14 (1), 10/07/2025 04:02 (10)
Complete: 🔍
Cache ID: 216:8BA: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.