dbcve.org
N2wApplication · N2ws

CVE-2025-59706

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 4.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In N2W before 4.3.2 and 4.4.0 before 4.4.1, improper validation of API request parameters enables remote code execution.

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

The N2W application fails to properly validate API request parameters, allowing attackers to inject malicious input that gets executed on the server. This improper input validation enables remote code execution without authentication, making it trivially exploitable given the 9.8 CVSS score.

MitigationUpgrade N2W to version 4.3.2 or 4.4.1 and later. If immediate patching is not feasible, restrict network access to API endpoints and implement web application firewall rules to filter malicious parameter patterns.

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
N2wApplication
Affected:< 4.3.2

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Confirm N2W installation
    Locate the N2W application installation directory or check running services for N2W/N2w processes. On Linux, check /opt/n2w or common application paths. On Windows, check Program Files for N2WS Backup and Recovery.
    Affected if N2W is not installed on the system
  2. Identify installed N2W version
    Check the N2W version by inspecting the application's about page, configuration file, or running the n2w --version command if available. Common version file locations include /opt/n2w/version or the application web interface.
    Affected if The installed version is lower than 4.3.2 (e.g., 4.3.1, 4.3.0, 4.2.x, or earlier)
  3. Verify API endpoint exposure
    Identify if N2W API endpoints are network-accessible. Check firewall rules, reverse proxy configurations, or network access control lists that allow external access to N2W API ports (typically 443 or 8443).
    Affected if API endpoints are reachable from untrusted networks without authentication restrictions
  4. Inspect API service status
    Confirm the N2W API service is running and enabled. Check system services (systemd, init.d) or the N2W admin console for API service status.
    Affected if API service is running and exposed

A system is affected if N2W is installed with a version lower than 4.3.2 and the API interface is network-accessible, allowing unauthenticated attackers to send malicious input leading to remote code execution.

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 4.3.2 or later
Fixed in 4.3.2
Interim mitigation

Upgrade N2W to version 4.3.2 or 4.4.1 and later. If immediate patching is not feasible, restrict network access to API endpoints and implement web application firewall rules to filter malicious parameter patterns.

Recommended fix High confidence

N2W 4.3.2 or later (4.3.x branch); N2W 4.4.1 (4.4.x branch)

  1. Identify the currently installed N2W version by checking the product UI or system information
  2. If running version 4.3.x (any version before 4.3.2), upgrade to version 4.3.2 or later
  3. If running version 4.4.0, upgrade to version 4.4.1
  4. After upgrade, verify the N2W service is running and accessible
  5. Confirm the API functionality is working as expected after the upgrade

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

Fix this in N2w Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59706 — 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-59706 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