Microsoft Windows up to Server 2025 SMB Client improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.8 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Microsoft Windows. This impacts an unknown function of the component SMB Client. The manipulation leads to an unknown weakness. This vulnerability is traded as CVE-2025-59280. It is possible to initiate the attack remotely. There is no exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Microsoft Windows and classified as problematic. This issue affects an unknown functionality of the component SMB Client. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is integrity. The summary by CVE is:
Improper authentication in Windows SMB Client allows an unauthorized attacker to perform tampering over a network.
The weakness was shared 10/14/2025 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2025-59280. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/21/2025).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 10
- 10 21H2
- 10 22H2
- 10 1607
- 10 1809
- 11 22H2
- 11 23H2
- 11 24H2
- Server 2008 R2 SP1
- Server 2008 SP2
- Server 2012
- Server 2012 R2
- Server 2016
- Server 2019
- Server 2022
- Server 2022 23H2
- Server 2025
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 2.8
VulDB Base Score: 3.1
VulDB Temp Score: 2.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 3.1
Vendor Vector (Microsoft): 🔒
CNA Base Score: 3.1
CNA Vector (Microsoft): 🔒
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: Improper authenticationCWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Unproven
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: PatchStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline
10/14/2025 VulDB entry created10/14/2025 Advisory disclosed
10/14/2025 Countermeasure disclosed
10/21/2025 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-59280 (🔒)
GCVE (CVE): GCVE-0-2025-59280
GCVE (VulDB): GCVE-100-328469
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 10/14/2025 20:18Updated: 10/21/2025 02:44
Changes: 10/14/2025 20:18 (20), 10/14/2025 20:19 (15), 10/14/2025 20:22 (33), 10/21/2025 02:44 (13)
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.