CVE-2026-7569
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 viewclient Cross-Site Scripting Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of Quest NetVault Backup. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the viewclient webpage. The issue results from the lack of proper validation of user-supplied data, which can lead to the injection of an arbitrary script. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-28202.
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's viewclient webpage suffers from a cross-site scripting (XSS) vulnerability due to insufficient validation of user-supplied input. This allows injection of arbitrary JavaScript into the page. The vulnerability requires user interaction (visiting a malicious page/file) but can be chained with other flaws to achieve SYSTEM-level code execution.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Verify Quest NetVault Backup is installedCheck for the installation directory (typically C:\Program Files\Quest\NetVault Backup or /opt/netvault) or look for the NetVault service running on the systemAffected if The product is not installed or no NetVault service is found, the system is not affected by this CVE
-
Determine installed versionLocate the version information - check the NetVault installation directory for a version file, or run 'nvtsa -v' or 'nvadmin -v' from the bin directory, or inspect the Windows registry under HKLM\SOFTWARE\Quest\NetVault\Backup\CurrentVersionAffected if The installed version is any version prior to 14.0.2 (e.g., 14.0.1, 14.0.0, 13.x, etc.)
-
Confirm viewclient web interface is accessibleCheck if the viewclient component is enabled by examining the NetVault configuration files (typically nvwebui.conf or similar in the config directory), or attempt to access the web interface on port 8443 or 2003 default portsAffected if The viewclient web interface is enabled and reachable on the network
-
Verify input validation configurationExamine the NetVault web server configuration files for any custom input validation or output encoding settings applied to the viewclient component. Look for any custom filter or sanitization rules in the web.xml or equivalent configurationAffected if No custom input validation or output encoding is configured for viewclient, leaving it vulnerable to XSS injection
A system is affected if Quest NetVault Backup version is below 14.0.2 AND the viewclient web interface is enabled and lacks custom input validation.
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
Implement strict input validation and output encoding on all user-supplied data within the viewclient component to prevent script injection. Consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.
NetVault Backup 14.0.2
- 1. Download NetVault Backup version 14.0.2 from the Quest support portal (support.quest.com)
- 2. Review the release notes and upgrade documentation specific to your current version
- 3. Schedule a maintenance window and backup all critical data
- 4. Stop the NetVault Backup services before upgrading
- 5. Run the installer for version 14.0.2
- 6. Follow the prompts to complete the upgrade
- 7. Restart NetVault Backup services
- 8. Verify the viewclient webpage functions correctly and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7569 — 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-7569 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