CVE-2025-48984
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 · uneditedA vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user.
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 a remote code execution vulnerability in a Backup Server product that allows an authenticated domain user to execute arbitrary code on the server. The vulnerability requires prior authentication, meaning the attacker needs valid domain credentials, but once authenticated they can inject and execute malicious code on the backup server infrastructure.
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>= 12.0.0.1402, < 12.3.2.4165CVSS 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.
-
Locate Veeam Backup & Replication installation pathCheck default installation directory C:\Program Files\Veeam\Backup and Replication\Backup\ or search for Veeam.Backup.Manager.exe in Program FilesAffected if Veeam installation found - proceed to version check
-
Determine installed Veeam versionRun Veeam Backup & Replication console and navigate to Help > About, or use PowerShell with command 'Get-VBRServerInfo' after importing VeeamPSSnapinAffected if Cannot determine - no Veeam installation found
-
Compare version to affected rangeRecord the full version number shown (format: xx.x.x.xxxx) and compare: affected if version is 12.0.0.1402 or higher AND version is lower than 12.3.2.4165Affected if Version falls within 12.0.0.1402 to 12.3.2.4164 inclusive
Environment is affected if Veeam Backup & Replication version is 12.0.0.1402 or higher but lower than 12.3.2.4165, and the server accepts authenticated domain user connections.
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 · scoped12.3.2.4165
Apply vendor-provided patches immediately and restrict backup server access to only necessary authenticated personnel. Review and audit domain user permissions to ensure the principle of least privilege is enforced.
Veeam Backup & Replication 12.3.2.4165 or later
- 1. Verify current Veeam Backup & Replication version by checking the console or running Get-VBRInstalledVersion command
- 2. Download Veeam Backup & Replication version 12.3.2.4165 or later from the official Veeam downloads portal
- 3. Review Veeam Backup & Replication 12.3.2 release notes for any prerequisites or known issues
- 4. Create a complete backup of the Veeam configuration database before upgrading
- 5. Schedule maintenance window as the upgrade may require downtime
- 6. Run the Veeam Backup & Replication installer and follow the upgrade wizard prompts
- 7. After upgrade completes, verify the new version by checking About section in Veeam console
- 8. Test critical backup and restore operations to ensure functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48984 — 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-48984 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