dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-34136

MEDIUM · 6.9 CVSS v4.0 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An SQL injection vulnerability exists in Commvault 11.32.0 - 11.32.93, 11.36.0 - 11.36.51, and 11.38.0 - 11.38.19 Web Server component that allows a remote, unauthenticated attacker to perform SQL Injection. The vulnerability impacts systems where the CommServe and Web Server roles are installed. Other Commvault components deployed in the same environment are not affected.

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 · high confidence

SQL injection vulnerability in Commvault Web Server component allows remote, unauthenticated attackers to inject malicious SQL queries. The flaw affects specific version ranges (11.32.0-11.32.93, 11.36.0-11.36.51, 11.38.0-11.38.19) when both CommServe and Web Server roles are installed on the same system.

MitigationApply vendor patches (11.32.94, 11.36.52, 11.38.20 or later) to remediate the SQL injection. Network segmentation may reduce exposure but is not a substitute for the required software update.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify CommVault installation and version
    Locate the CommVault installation directory and check the version. Typically found in the installation path (e.g., C:\Program Files\CommVault\ContentStore\Base or similar). Look for version.txt or check the CommServe console for the exact version number.
    Affected if Installed version falls within 11.32.0-11.32.93, 11.36.0-11.36.51, or 11.38.0-11.38.19
  2. Verify CommServe and Web Server roles on the same system
    Open the CommVault CommServe console or use the command line tool (cvinfo.exe) to list installed components and roles. Check if both the CommServe component and Web Server component are present on the same server.
    Affected if Both CommServe and Web Server roles are installed on the same system (the vulnerable configuration)
  3. Check Web Server component accessibility
    Identify the Web Server port (typically 80/443 or custom ports). Check network exposure by reviewing firewall rules and listening services (netstat -an | findstr LISTENING). Determine if the Web Server is accessible from external/untrusted networks.
    Affected if The Web Server component is exposed to remote, unauthenticated network access (not restricted to localhost or trusted internal networks)

A system is affected if it runs a CommVault version within 11.32.0-11.32.93, 11.36.0-11.36.51, or 11.38.0-11.38.19 AND has both CommServe and Web Server roles installed on the same host with the Web Server accessible to remote attackers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches (11.32.94, 11.36.52, 11.38.20 or later) to remediate the SQL injection. Network segmentation may reduce exposure but is not a substitute for the required software update.

Recommended fix Moderate confidence

Upgrade to Commvault 11.32.94+, 11.36.52+, or 11.38.20+ (depending on your current branch)

  1. Identify the currently installed Commvault version by checking the CommServe and Web Server components
  2. Determine which version branch (11.32.x, 11.36.x, or 11.38.x) is currently deployed
  3. For 11.32.x branch: upgrade to version 11.32.94 or later
  4. For 11.36.x branch: upgrade to version 11.36.52 or later
  5. For 11.38.x branch: upgrade to version 11.38.20 or later
  6. Verify the upgrade was successful by confirming the Commvault Web Server component is running the patched version
  7. Test that critical Commvault functionality (backup, restore, indexing) continues to work after the upgrade
Caveat Review Commvault release notes for any compatibility changes or deprecated features before upgrading; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34136 — 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-34136 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