CVE-2025-57789
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 · uneditedDuring the brief window between installation and the first administrator login, remote attackers may exploit the default credential to gain admin control. This is limited to the setup phase, before any jobs have been configured.
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 confidenceA default credential vulnerability exists in the initial setup phase between software installation and first administrator login. Remote attackers can exploit this window to gain administrative control using the default credential, but this is limited to systems that have not yet completed initial configuration with custom admin credentials.
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.36.60CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Commvault installation and versionUse system inventory tools or check installed programs list to determine if Commvault Commvault is present and note its installed version numberAffected if The installed version is below 11.36.60
-
Determine if initial administrator setup is completeCheck whether the system has completed first-time setup by attempting to access the admin console or checking configuration state files/registry for signs that custom admin credentials have been configuredAffected if The system shows no evidence that custom administrator credentials were configured after installation, meaning default credentials may still be active
-
Verify default admin account statusExamine user/account management within Commvault to determine whether the default administrative account remains enabled or unchanged from factory defaultsAffected if The default administrative account is still active or unchanged from installation defaults
A user is affected if Commvault version is below 11.36.60 AND the initial administrator setup with custom credentials has not been completed, leaving default credentials active.
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.36.60
Immediately complete the administrator setup process after installation and change any default credentials before exposing the system to network access. Network isolation during initial setup is recommended as an additional safeguard.
11.36.60
- Backup your current Commvault configuration and database before proceeding with the upgrade
- Download Commvault version 11.36.60 or later from the official Commvault documentation site (documentation.commvault.com)
- Stop all Commvault services on the server before running the upgrade
- Run the installer for version 11.36.60 and follow the on-screen upgrade prompts
- After upgrade completion, start Commvault services and verify the installation was successful
- During the initial setup wizard, ensure you configure a strong, unique administrator password instead of using any default credentials
- Verify that the web console is accessible and the upgrade was applied correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57789 — 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-57789 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