XML External Entity (XXE)Weakness · CWE-611

CVE-2025-32406

HIGH · 8.6 CVSS v3.1 Published 2025-04-08

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

An XXE issue in the Director NBR component in NAKIVO Backup & Replication 10.3.x through 11.0.1 before 11.0.2 allows remote attackers fetch and parse the XML response.

Technical summary

dbcve analysis · high confidence

An XXE (XML External Entity) injection vulnerability in the Director NBR component of NAKIVO Backup & Replication versions 10.3.x through 11.0.1 allows remote attackers to craft malicious XML requests that can fetch and parse internal XML responses, potentially leading to sensitive data disclosure or server-side request forgery. The vulnerability is fixed in version 11.0.2.

MitigationUpgrade NAKIVO Backup & Replication to version 11.0.2 or later to remediate this XXE vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if NAKIVO Backup & Replication is installed

Check for the installation by looking for the NAKIVO installation directory (commonly at C:\Program Files\NAKIVO\Backup & Replication on Windows or /opt/nakivo on Linux) and verify the Director service is running.

Affected if NAKIVO Backup & Replication software is present on the system
Determine the installed version of NAKIVO Backup & Replication

Access the Director web interface (typically https://<hostname>:4443 or https://<hostname>/director) and navigate to the About or Settings section to view the exact version number, or check the version file in the installation directory.

Affected if The installed version is 10.3.x, 10.4.x, 10.5.x, 10.6.x, 10.7.x, 10.8.x, 10.9.x, 10.10.x, 10.11.x, or any version from 10.3.0 through 11.0.1 inclusive
Verify the Director NBR component is accessible

Attempt to access the Director web interface over HTTPS on the configured port (default 4443) and confirm the service responds to HTTP requests.

Affected if The Director NBR component is running and accepts HTTP/HTTPS connections
Check if XML-based API or functionality is exposed

Review the Director NBR component configuration to determine if XML request handling is enabled, typically accessible via the API endpoints under the Director service.

Affected if The Director NBR component processes XML requests from remote clients

You are affected if NAKIVO Backup & Replication version 10.3.0 through 11.0.1 is installed and the Director NBR component is accessible and processing XML requests.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade NAKIVO Backup & Replication to version 11.0.2 or later to remediate this XXE vulnerability.

Recommended fix High confidence

11.0.2

Back up your current NAKIVO Backup & Replication configuration and data before upgrading
Download NAKIVO Backup & Replication version 11.0.2 from the official vendor site or your licensed download location
Plan a maintenance window - the Director service will be unavailable during the upgrade
Run the installer/upgrader to upgrade the Director NBR component to version 11.0.2
After upgrade completes, verify the Director service is running and accessible
Log in to the Director web interface and confirm all backup jobs and repositories are intact
Review release notes or security advisories to confirm the XXE vulnerability is addressed in 11.0.2

Caveat Review release notes for any deprecated features or breaking changes between your current version and 11.0.2 before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

12.0 hours of engineering $2,130

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-32406 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

helpcenter.nakivo.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32406 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-32406?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 8.6 High

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

A high-priority fix

Have this fixed 12 hrs · Moderate

Typical engagement from $2,130

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-32406 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References