| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Teams. It has been classified as problematic. Impacted is an unknown function. The manipulation leads to insufficient permissions or privileges. This vulnerability is documented as CVE-2025-49731. The attack can be initiated remotely. There is not any exploit available. It is recommended to apply a patch to fix this issue.
Details
A vulnerability, which was classified as problematic, has been found in Microsoft Teams (unknown version). This issue affects an unknown code block. The manipulation with an unknown input leads to a insufficient permissions or privileges vulnerability. Using CWE to declare the problem leads to CWE-280. The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state. Impacted is confidentiality. The summary by CVE is:
Improper handling of insufficient permissions or privileges in Microsoft Teams allows an authorized attacker to elevate privileges over a network.
The weakness was released 07/08/2025 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. The identification of this vulnerability is CVE-2025-49731. The exploitation is known to be difficult. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/13/2026). The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.
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 EUVD (EUVD-2025-20621). Be aware that VulDB is the high quality 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: 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: Insufficient permissions or privilegesCWE: CWE-280 / CWE-266
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
07/08/2025 VulDB entry created07/08/2025 Advisory disclosed
07/08/2025 Countermeasure disclosed
02/13/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-49731 (🔒)
GCVE (CVE): GCVE-0-2025-49731
GCVE (VulDB): GCVE-100-315551
EUVD: 🔒
Entry
Created: 07/08/2025 19:56Updated: 02/13/2026 16:03
Changes: 07/08/2025 19:56 (34), 07/08/2025 20:00 (34), 07/11/2025 19:22 (1), 02/13/2026 16:03 (12)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.