| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Microsoft Azure Cosmos DB. The impacted element is an unknown function. The manipulation leads to cross site scripting. This vulnerability is listed as CVE-2025-64675. The attack may be initiated remotely. There is no available exploit. This product is a managed service. This means that users are not able to maintain vulnerability countermeasures themselves.
Details
A vulnerability was found in Microsoft Azure Cosmos DB (version now known). It has been rated as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
Improper neutralization of input during web page generation ('cross-site scripting') in Azure Cosmos DB allows an unauthorized attacker to perform spoofing over a network.
The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2025-64675 since 11/07/2025. The exploitation is known to be easy. 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 $0-$5k at the moment (estimation calculated on 01/16/2026). MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-204423) and CERT Bund (WID-SEC-2025-2890). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Microsoft Azure Cosmos DB
- Microsoft Azure
Product
Type
Vendor
Name
License
Managed Service
- yes
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.6
NVD Vector: 🔒
CNA Base Score: 8.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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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
Status: 🔍0-Day Time: 🔒
Timeline
11/07/2025 CVE reserved12/19/2025 Advisory disclosed
12/19/2025 VulDB entry created
01/16/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-64675 (🔒)
GCVE (CVE): GCVE-0-2025-64675
GCVE (VulDB): GCVE-100-337553
EUVD: 🔒
CERT Bund: WID-SEC-2025-2890 - Microsoft Azure Komponenten: Mehrere Schwachstellen
Entry
Created: 12/19/2025 08:17Updated: 01/16/2026 19:42
Changes: 12/19/2025 08:17 (62), 12/20/2025 06:41 (7), 01/15/2026 00:54 (1), 01/16/2026 19:42 (11)
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.