Microsoft Exchange Server improper validation of syntactic correctness of input
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $5k-$25k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Microsoft Exchange Server. Impacted is an unknown function. Executing a manipulation can lead to improper validation of syntactic correctness of input. This vulnerability appears as CVE-2025-25007. The attack may be performed from remote. There is no available exploit. It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Microsoft Exchange Server (the affected version unknown). It has been declared as problematic. This vulnerability affects an unknown part. The manipulation with an unknown input leads to a improper validation of syntactic correctness of input vulnerability. The CWE definition for the vulnerability is CWE-1286. The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax. As an impact it is known to affect integrity. CVE summarizes:
Improper validation of syntactic correctness of input in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.
The weakness was presented 08/12/2025 as confirmed security update guide (Website). The advisory is shared for download at msrc.microsoft.com. This vulnerability was named CVE-2025-25007. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 09/03/2025).
The vulnerability scanner Nessus provides a plugin with the ID 249140 (Security Updates for Microsoft Exchange Server (August 2025)), which helps to determine the existence of the flaw in a target environment.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (249140). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 5.3
Vendor Vector (Microsoft): 🔍
CNA Base Score: 5.3
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 validation of syntactic correctness of inputCWE: CWE-1286 / CWE-20
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 |
Nessus ID: 249140
Nessus Name: Security Updates for Microsoft Exchange Server (August 2025)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
08/12/2025 🔍08/12/2025 🔍
08/12/2025 🔍
09/03/2025 🔍
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-25007 (🔍)
GCVE (CVE): GCVE-0-2025-25007
GCVE (VulDB): GCVE-100-319588
Entry
Created: 08/12/2025 19:15Updated: 09/03/2025 17:12
Changes: 08/12/2025 19:15 (34), 08/12/2025 19:19 (34), 08/13/2025 06:05 (2), 09/03/2025 17:12 (12)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.