CVE-2025-32991
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 · uneditedIn N2WS Backup & Recovery before 4.4.0, a two-step attack against the RESTful API results in 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 confidenceN2WS Backup & Recovery contains a critical vulnerability in its RESTful API where a two-step attack chain allows remote code execution. The specific attack sequence and affected API endpoints are not detailed in available sources, but the vulnerability is present in versions prior to 4.4.0.
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< 4.3.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 N2WS Backup & Recovery installation versionAccess the product web UI dashboard or run the command 'n2ws --version' or 'rpm -q n2ws' from the appliance terminal to retrieve the installed version numberAffected if The displayed version is lower than 4.3.2 (e.g., 4.3.1, 4.2.x, etc.)
-
Confirm RESTful API is enabledNavigate to the product settings or configuration panel in the web UI, or inspect the configuration file (typically in /opt/n2ws/etc/ or the product config directory) for APIEnable or REST API settingsAffected if The RESTful API service is in an enabled or active state, exposing API endpoints to the network
-
Verify API access controlsCheck the API authentication configuration in the web UI under API settings or review the API configuration file for any authentication bypass or weak access control settingsAffected if The API is accessible without proper authentication or uses default/weak credentials, making the two-step attack chain feasible
-
Review API endpoint exposureExamine network configuration to determine if the API service is bound to a non-internal interface or accessible from external IPs, using 'netstat -tlnp | grep api' or reviewing firewall rulesAffected if The RESTful API is listening on a public or untrusted network interface rather than localhost only
The environment is affected if N2WS Backup & Recovery version is below 4.3.2 AND the RESTful API is enabled and accessible, as the two-step RCE attack chain targets the API component.
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 · scoped4.3.2
Upgrade N2WS Backup & Recovery to version 4.4.0 or later to remediate this vulnerability.
4.4.0 or later
- Upgrade N2WS Backup & Recovery to version 4.4.0 or later to remediate the remote code execution vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32991 — 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-32991 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