dbcve.org
N CentralApplication · N Able

CVE-2025-11700

HIGH · 7.5 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 2025.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
N-central versions < 2025.4 are vulnerable to multiple XML External Entities injection leading to information disclosure

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 confidence

N-central versions prior to 2025.4 contain multiple XML External Entities (XXE) injection vulnerabilities. Attackers can exploit the application's XML parser by injecting malicious external entity references within crafted XML requests, potentially reading local files or performing server-side request forgery leading to information disclosure.

MitigationUpgrade N-central to version 2025.4 or later. If immediate patching is not feasible, disable external entity processing in the XML parser configuration and implement strict input validation for all XML-handling endpoints.

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
N CentralApplication
Affected:< 2025.4

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Confirm N-central is installed
    Locate the N-central installation directory or check for the N-central service running on the system. Common locations include C:\Program Files\N-able\N-central or /opt/nable/ncentral/. Verify the service is active.
    Affected if The N-central application is installed and running on the system.
  2. Identify the installed N-central version
    Access the N-central web interface and navigate to the About or System Information page, or check the version file within the installation directory. Note the exact version number displayed.
    Affected if The installed version is lower than 2025.4 (e.g., 2025.3, 2025.2, earlier releases).
  3. Locate XML parser configuration
    Examine the XML parser settings within the N-central configuration files. Look for configuration parameters related to XML processing, external entity handling, or document type definition (DTD) processing in the conf or config subdirectory.
    Affected if The XML parser is configured to allow external entity processing or DTD parsing, which is the default vulnerable state in affected versions.
  4. Identify XML-handling endpoints
    Review the N-central configuration or documentation to identify endpoints, APIs, or features that accept XML input. Check for web services, import functions, or integration points that process XML data.
    Affected if XML-handling endpoints are exposed and accepting XML input without strict input validation enabled.

A user is affected if their N-central installation version is below 2025.4 and the XML parser has external entity processing enabled or accessible XML-handling endpoints exist.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.4 or later
Fixed in 2025.4
Interim mitigation

Upgrade N-central to version 2025.4 or later. If immediate patching is not feasible, disable external entity processing in the XML parser configuration and implement strict input validation for all XML-handling endpoints.

Recommended fix Moderate confidence

2025.4

  1. Backup the current N-central installation and all critical data
  2. Review the N-central 2025.4 release notes on me.n-able.com for any prerequisites or migration requirements
  3. Download N-central version 2025.4 from the vendor's official portal (me.n-able.com)
  4. Follow N-able's documented upgrade procedure to apply version 2025.4
  5. Verify the upgrade completed successfully and confirm the XXE vulnerability is remediated
Caveat Review 2025.4 release notes for any breaking changes or required migration steps before upgrading

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

Fix this in N Central Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing5.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11700 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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