dbcve.org
CommvaultApplication

CVE-2025-57791

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 11.36.60 or later.
See remediation →
74/100
Remediation priority · Elevated
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
A security vulnerability has been identified that allows remote attackers to inject or manipulate command-line arguments passed to internal components due to insufficient input validation. Successful exploitation results in a valid user session for a low privilege role.

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

This is a command-line argument injection vulnerability where remote attackers can manipulate arguments passed to internal components due to insufficient input validation. Successful exploitation grants a valid user session with low-privilege role access.

MitigationImplement strict input validation and sanitization for all user-supplied data used in command-line arguments, and follow the principle of least privilege to limit session capabilities.

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
CommvaultApplication
Affected:< 11.36.60

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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 version
    Use the Commvault command-line interface or check the software release version through the administration console. Typical commands include 'commvault -version' or checking the About section in the GUI.
    Affected if The installed version is below 11.36.60
  2. Locate user input acceptance points
    Review web console, API endpoints, and CLI interfaces that accept user-supplied data, particularly those handling search queries, file paths, or session parameters.
    Affected if User-accessible input fields exist that could pass data to internal command execution paths
  3. Audit command execution pathways
    Inspect any custom scripts, integrations, or configured jobs that accept user parameters and construct command-line arguments from them.
    Affected if User-supplied parameters can be injected into command-line arguments without proper sanitization
  4. Review session creation mechanisms
    Examine how user sessions are created and what parameters are accepted during session initialization, focusing on low-privilege role configurations.
    Affected if Session creation accepts manipulatable arguments that could be injected into command execution

The environment is affected if the installed Commvault version is below 11.36.60 AND the system allows user-supplied input to reach internal command-line argument processing without validation.

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
Upgrade available Upgrade to 11.36.60 or later
Fixed in 11.36.60
Interim mitigation

Implement strict input validation and sanitization for all user-supplied data used in command-line arguments, and follow the principle of least privilege to limit session capabilities.

Recommended fix High confidence

Commvault version 11.36.60

  1. 1. Identify all Commvault installations in your environment running version below 11.36.60
  2. 2. Review the Commvault upgrade documentation at documentation.commvault.com for upgrade procedures
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Back up current configuration and database as recommended in upgrade documentation
  5. 5. Upgrade Commvault to version 11.36.60 or later
  6. 6. Verify the upgrade was successful by checking the version number in the Commvault console
  7. 7. Test critical backup and restore operations to ensure functionality

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

Fix this in Commvault Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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