CVE-2025-3928
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 · uneditedCommvault 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.
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 confidenceCommvault Web Server contains a vulnerability allowing remote authenticated attackers to compromise webservers by creating and executing webshells, enabling arbitrary code execution on the affected system.
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.20.0, < 11.20.217>= 11.28.0, < 11.28.141>= 11.32.0, < 11.32.89>= 11.36.0, < 11.36.46CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Check Commvault versionLocate the Commvault installation and retrieve the installed version number. On Windows this may be in the registry or via the command 'commvault version' if the CLI is available. On Linux check /opt/commvault or the installation directory for version info.Affected if The installed version falls within any of these ranges: 11.20.0-11.20.216, 11.28.0-11.28.140, 11.32.0-11.32.88, or 11.36.0-11.36.45.
-
Identify exposed Web Server componentDetermine if the Commvault Web Server (Commvault REST API or Web Console) is exposed to the network. Review firewall rules, reverse proxy configurations, and network segmentation around the Commvault server.Affected if The Web Server component is internet-facing or accessible from untrusted network segments.
-
Review web server logs for suspicious file uploadsExamine Commvault Web Server access and error logs for unusual HTTP requests, particularly POST requests to unknown paths, or requests containing file upload patterns. Check logs in the Commvault logs directory for entries referencing .jsp, .asp, .php, or other executable file extensions.Affected if Logs show unexpected file upload requests or creation of files in web-accessible directories.
-
Scan web directories for unauthorized webshellsSearch web application directories (particularly the Commvault web root or document root) for newly created or unexpected script files with extensions such as .jsp, .asp, .php, .exe, or .cmd. Compare current files against a known-good baseline if available.Affected if Unexpected executable files are found in web-accessible directories, especially with recent modification dates.
-
Verify authentication and user account integrityReview Commvault user accounts for unauthorized additions or modifications. Check for new administrative accounts or accounts with elevated privileges that were not created by legitimate administrators.Affected if Unexpected user accounts exist in Commvault, or existing accounts show privilege escalation or unusual login activity.
A user is affected if their Commvault installation version is below the fixed versions AND the Web Server component is accessible to authenticated attackers who could potentially deploy webshells.
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.20.21711.28.14111.32.89
Upgrade Commvault to version 11.36.46, 11.32.89, 11.28.141, or 11.20.217 (depending on current version line) for Windows and Linux platforms. This is a CISA KEV-listed vulnerability requiring urgent remediation.
Upgrade to version 11.36.46 (or 11.32.89, 11.28.141, or 11.20.217 depending on your current version branch)
- 1. Identify the current Commvault version by checking the Commcell Console or running 'commvault version' command
- 2. Determine which version branch you're currently on (11.20.x, 11.28.x, 11.32.x, or 11.36.x) to select the appropriate fixed release
- 3. Create a full backup of the Commvault environment including the database and configuration
- 4. Download the corresponding fixed version from Commvault Support: 11.20.217, 11.28.141, 11.32.89, or 11.36.46
- 5. Review Commvault upgrade documentation for your platform (Windows or Linux) at documentation.commvault.com
- 6. Apply the upgrade during a maintenance window following standard Commvault upgrade procedures
- 7. After upgrade, verify the version matches the expected fixed release
- 8. Confirm the webshell vulnerability is remediated by reviewing Commvault security advisory
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3928 — 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-3928 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