CVE-2026-7570
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 · uneditedQuest NetVault Backup NVBUDashboard SQL Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Quest NetVault Backup. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the processing of NVBUDashboard JSON-RPC messages. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of NETWORK SERVICE. Was ZDI-CAN-27809.
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 confidenceQuest NetVault Backup contains a SQL injection vulnerability in the NVBUDashboard JSON-RPC message processing function. The application fails to properly validate user-supplied input before using it in SQL query construction. Additionally, the authentication mechanism can be bypassed, allowing unauthenticated attackers to exploit the SQL injection and achieve remote code execution as the NETWORK SERVICE account.
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< 14.0.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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.
-
Identify NetVault Backup installation and versionLocate the NetVault Backup installation directory and find the version information, typically in the main executable or a version file within the program folderAffected if NetVault Backup is installed and the version is below 14.0.2
-
Verify NVBUDashboard service statusCheck if the NVBUDashboard service is running on the system, typically as a Windows serviceAffected if The NVBUDashboard service is installed and running
-
Confirm JSON-RPC interface exposureDetermine if the NVBUDashboard JSON-RPC interface is network-accessible, typically listening on a TCP portAffected if The JSON-RPC interface is exposed to the network or untrusted hosts
-
Review authentication configurationExamine the NVBUDashboard authentication settings to determine if the authentication bypass is possibleAffected if Authentication is configured in a way that allows bypass or uses default credentials
-
Inspect logs for SQL injection indicatorsSearch NVBUDashboard and database logs for suspicious SQL query patterns, unexpected SQL syntax, or anomalous database requestsAffected if Logs contain unusual SQL statements or injection attempt signatures
The environment is affected if Quest NetVault Backup is installed with a version lower than 14.0.2 and the NVBUDashboard JSON-RPC interface is accessible, regardless of authentication status since bypass is possible.
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 · scoped14.0.2
Apply the vendor patch when available; if no patch exists, implement parameterized queries/prepared statements for all database operations in the JSON-RPC handler and fix the authentication bypass logic.
14.0.2
- 1. Obtain Quest NetVault Backup version 14.0.2 or later from the official Quest support portal at support.quest.com
- 2. Review the upgrade documentation and release notes for NetVault Backup 14.0.2
- 3. Ensure you have a complete backup of the NetVault Backup configuration and database
- 4. Schedule a maintenance window to minimize disruption
- 5. Stop the NetVault Backup services before performing the upgrade
- 6. Install NetVault Backup version 14.0.2 following the documented upgrade procedure
- 7. After installation, verify that the NVBUDashboard service is running correctly
- 8. Confirm the upgrade was successful by checking the NetVault Backup version in the web interface or CLI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7570 — 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-2026-7570 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