CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2025-3928 remediation guide

Commvault Web Server

Commvault Web Server has an unspecified vulnerability that can be exploited by a remote, authenticated attacker. According to the Commvault advisory: "Webservers can be compromised through bad actors creating and executing webshells." Fixed in version 11.36.46, 11.32.89, 11.28.141, and 11.20.217 for Windows and Linux platforms. This vulnerability was added to the CISA Known Exploited Vulnerabilities (KEV) Catalog on 2025-04-28.

Open CVE record
ProductCommvault Web Server
Affected versions11.36.0, 11.32.0, 11.28.0, 11.20.0, >= 11.20.0 < 11.20.217, >= 11.28.0 < 11.28.141, >= 11.32.0 < 11.32.89, >= 11.36.0 < 11.36.46
Fixed versions11.20.217, 11.28.141, 11.32.89, 11.36.46
Priority basisImmediate · CVSS 8.7 · EPSS 2.09%
01

Identify the affected asset

Confirm whether Commvault Web Server is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 11.36.0, 11.32.0, 11.28.0, 11.20.0, >= 11.20.0 < 11.20.217, >= 11.28.0 < 11.28.141, >= 11.32.0 < 11.32.89, >= 11.36.0 < 11.36.46. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.