CVE-2025-59468
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 · uneditedThis vulnerability allows a Backup Administrator to perform remote code execution (RCE) as the postgres user by sending a malicious password parameter.
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 confidenceThis is an authenticated command injection vulnerability in backup functionality that allows a Backup Administrator to achieve remote code execution as the postgres user by injecting malicious commands through a password parameter. The vulnerability stems from improper input sanitization when processing the password field during backup operations.
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>= 13.0.0.4967, < 13.0.1.1071CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify installed Veeam Backup & Replication versionOpen Veeam Backup & Replication console, go to Help > About, or run 'veeamversion' from command line. Alternatively, check Windows Programs and Features for the installed version number.Affected if Installed version is >= 13.0.0.4967 and < 13.0.1.1071
-
Confirm Backup Administrator role accessIn Veeam console, navigate to Users and Roles to verify if any user accounts are assigned the Backup Administrator role. This role is required to trigger the vulnerable backup functionality.Affected if Any user has Backup Administrator role assigned and the Veeam version is in the affected range
-
Review backup job configurationsOpen Veeam Backup & Replication > Backup Jobs. Examine any configured backup jobs, particularly those using password-protected repositories or credentials in backup storage settings.Affected if Backup jobs exist using password-protected storage or credential entries, combined with affected version
-
Audit backup activity logs for unusual entriesIn Veeam console, go to History > Backup or Job Sessions. Review logs around backup operations, specifically looking for unexpected commands or errors related to password field processing.Affected if Logs show anomalies in backup operations involving password parameters, especially if running as postgres user context
User is affected if Veeam Backup & Replication version falls within 13.0.0.4967 through 13.0.1.1070 and any Backup Administrator-accessible backup job uses password-protected storage.
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 · scoped13.0.1.1071
Implement strict input validation and proper escaping/parameterization for all user-controlled parameters in backup functions to prevent command injection. Consider using parameterized queries or prepared statements instead of concatenating user input into system commands.
Veeam Backup & Replication 13.0.1.1071 or later
- Schedule a planned maintenance window for the Veeam Backup & Replication upgrade
- Back up the Veeam configuration database before proceeding with the upgrade
- Download Veeam Backup & Replication version 13.0.1.1071 or later from the official Veeam website (www.veeam.com)
- Run the installer on the Veeam Backup & Replication server and follow the upgrade wizard prompts
- Complete the upgrade and verify all services start correctly
- Confirm the installed version is 13.0.1.1071 or later using the Veeam Backup & Replication console or version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-59468 — 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-59468 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