| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Microsoft Exchange Server. This issue affects some unknown processing. Performing a manipulation results in improper handling of additional special element. This vulnerability is reported as CVE-2025-25006. The attack is possible to be carried out remotely. No exploit exists. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in Microsoft Exchange Server (affected version not known). It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a improper handling of additional special element vulnerability. CWE is classifying the issue as CWE-167. The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided. This is going to have an impact on integrity. The summary by CVE is:
Improper handling of additional special element in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.
The weakness was disclosed 08/12/2025 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2025-25006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (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). Statistical analysis made it clear that VulDB provides the best quality 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 handling of additional special elementCWE: CWE-167 / 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 VulDB entry created08/12/2025 Advisory disclosed
08/12/2025 Countermeasure disclosed
09/03/2025 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-25006 (🔒)
GCVE (CVE): GCVE-0-2025-25006
GCVE (VulDB): GCVE-100-319587
Entry
Created: 08/12/2025 19:15Updated: 09/03/2025 17:12
Changes: 08/12/2025 19:15 (34), 08/12/2025 19:18 (34), 08/13/2025 06:05 (2), 09/03/2025 17:12 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.