CVE-2025-34028
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 · uneditedThe Commvault Command Center Innovation Release allows an unauthenticated actor to upload ZIP files that represent install packages that, when expanded by the target server, are vulnerable to path traversal vulnerability that can result in Remote Code Execution via malicious JSP. This issue affects Command Center Innovation Release: 11.38.0 to 11.38.20. The vulnerability is fixed in 11.38.20 with SP38-CU20-433 and SP38-CU20-436 and also fixed in 11.38.25 with SP38-CU25-434 and SP38-CU25-438.
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 confidenceUnauthenticated path traversal vulnerability in Commvault Command Center allows attackers to upload malicious ZIP install packages that, when extracted by the server, can write arbitrary files to arbitrary locations via directory traversal sequences, enabling deployment of malicious JSP webshells for remote code execution.
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>= 11.38.0, < 11.38.20CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine Commvault versionRun the command 'commvault -version' from the server command line, or log into Commvault Command Center and navigate to About/Version in the Help or System settings to view the installed version.Affected if The installed version is 11.38.0 through 11.38.19 (greater than or equal to 11.38.0 but less than 11.38.20)
-
Confirm Command Center web interface is activeCheck if the Commvault Command Center web service is running and accessible. Look for the web process (typically cvfwd or similar) and verify the web port (default 80/443 or configured custom port) is listening.Affected if Command Center web interface is running and listening on a network port
-
Verify ZIP install package feature is accessibleIn Command Center, check if the 'Install Package' or 'Deploy Package' feature under any software deployment or configuration section is present and available to unauthenticated users.Affected if The ZIP install package upload functionality is available (this is the vulnerable component)
-
Review network exposure of Command CenterExamine firewall rules, reverse proxies, or network access controls to determine if Command Center is exposed to untrusted networks or the internet.Affected if Command Center is reachable from outside the trusted internal network
The environment is affected by CVE-2025-34028 if the installed Commvault version is 11.38.0 through 11.38.19 and the Command Center web interface with the ZIP install package feature is accessible to network attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.38.20
Upgrade to Commvault 11.38.20 with SP38-CU20-433 or SP38-CU20-436, or 11.38.25 with SP38-CU25-434 or SP38-CU25-438 or later; alternatively, restrict unauthenticated access to Command Center until patching is possible.
Upgrade to Commvault 11.38.20 (with SP38-CU20-433 or SP38-CU20-436) or 11.38.25 (with SP38-CU25-434 or SP38-CU25-438)
- Identify current Commvault Command Center version using the web interface or command line
- Download the appropriate upgrade package from Commvault support portal: either version 11.38.20 with hotfixes SP38-CU20-433 and SP38-CU20-436, or version 11.38.25 with hotfixes SP38-CU25-434 and SP38-CU25-438
- Review Commvault upgrade documentation and release notes for pre-upgrade requirements
- Create a full backup of the Commvault environment and database
- Schedule maintenance window as upgrade will require service interruption
- Stop all Commvault services on the server before upgrading
- Install the selected fixed version (11.38.20 or 11.38.25) following standard Commvault upgrade procedures
- Apply the specific hotfix (SP38-CU20-433/436 or SP38-CU25-434/438) after base installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34028 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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