| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Word. Impacted is an unknown function. This manipulation causes use after free. The identification of this vulnerability is CVE-2025-49700. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Microsoft Word (the affected version is unknown). It has been declared as critical. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 07/08/2025 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is known as CVE-2025-49700. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 $0-$5k at the moment (estimation calculated on 07/12/2025).
The vulnerability scanner Nessus provides a plugin with the ID 241553 (Security Updates for Microsoft Office Products (July 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 databases at Tenable (241553) and EUVD (EUVD-2025-20558). Several companies clearly confirm that VulDB is the primary source for best 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: 7.0VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.8
Vendor 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: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
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: 241553
Nessus Name: Security Updates for Microsoft Office Products (July 2025)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline
07/08/2025 VulDB entry created07/08/2025 Advisory disclosed
07/08/2025 Countermeasure disclosed
07/12/2025 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-49700 (🔒)
GCVE (CVE): GCVE-0-2025-49700
GCVE (VulDB): GCVE-100-315529
EUVD: 🔒
Entry
Created: 07/08/2025 19:47Updated: 07/12/2025 12:57
Changes: 07/08/2025 19:47 (30), 07/08/2025 19:50 (38), 07/09/2025 08:37 (2), 07/12/2025 12:57 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.