dbcve.org
Azure Cosmos DbApplication · Microsoft

CVE-2025-64675

CRITICAL · 9.6 CVSS v3.1 Published 2025-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A cross-site scripting (XSS) vulnerability in Azure Cosmos DB allows an unauthenticated attacker to inject malicious scripts into web pages generated by the database interface. The 9.6 CVSS score indicates the flaw is easily exploitable over the network and enables session spoofing, potentially allowing attackers to steal credentials or impersonate legitimate users.

MitigationApply Microsoft's security patch for Azure Cosmos DB when released; verify that input validation and output encoding are properly implemented in any custom queries or interfaces interacting with the affected components.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure Cosmos DbApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Azure Cosmos DB deployment exists
    Search your Azure subscriptions for Cosmos DB resources using Azure Portal, CLI ('az cosmosdb list'), or infrastructure-as-code templates. Look for resource type 'Microsoft.DocumentDB/databaseAccounts'.
    Affected if Any Azure Cosmos DB account exists in your subscriptions, regardless of configuration.
  2. Identify exposed Data Explorer endpoints
    In Azure Portal, navigate to each Cosmos DB account > Data Explorer. Check if 'Enable public access' or similar settings are enabled. Also review network configuration under 'Firewalls and virtual networks' to see which IP ranges or endpoints can reach the web interfaces.
    Affected if The Data Explorer web interface is internet-accessible without restrictions.
  3. Review custom JavaScript or UDFs in databases
    Use Azure Portal Data Explorer or Cosmos DB SDK to list User-Defined Functions (UDFs), Stored Procedures, and any custom JavaScript registered in your databases. Query system containers or use DB shell commands to enumerate these.
    Affected if Custom JavaScript functions, UDFs, or stored procedures exist that handle user input without sanitization.
  4. Check Data Explorer settings for script execution
    In Azure Portal, go to Cosmos DB account > Settings > Data Explorer. Look for options like 'Script execution' or 'Query scripting' that may allow running arbitrary JavaScript. Verify if 'Enable scripting' is set to true.
    Affected if Script execution features in Data Explorer are enabled and accessible to users.
  5. Audit access control and authentication settings
    Review Cosmos DB account 'Keys' and 'Identity' settings. Check if primary/secondary keys or Microsoft Entra ID authentication is required for Data Explorer access. Look for any misconfigured RBAC roles under 'Access control (IAM)'.
    Affected if Data Explorer or REST APIs can be accessed without proper authentication or with overly permissive key settings.

A user is affected if they have any Azure Cosmos DB resource with an exposed Data Explorer or web interface, or if custom JavaScript/UDFs handle input without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft's security patch for Azure Cosmos DB when released; verify that input validation and output encoding are properly implemented in any custom queries or interfaces interacting with the affected components.

Fix this in Azure Cosmos Db Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64675 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64675 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data