CVE-2025-6798
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 · uneditedMarvell QConvergeConsole deleteAppFile Directory Traversal Arbitrary File Deletion Vulnerability. This vulnerability allows remote attackers to delete arbitrary files on affected installations of Marvell QConvergeConsole. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the deleteAppFile method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to delete files in the context of SYSTEM. Was ZDI-CAN-24918.
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 · high confidenceA directory traversal vulnerability exists in the deleteAppFile method of Marvell QConvergeConsole where user-supplied path input is not validated before being used in file deletion operations. This allows unauthenticated remote attackers to delete arbitrary files on the system with SYSTEM privileges.
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<= 5.5.0.85CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm QConvergeConsole is installedCheck for QConvergeConsole installation directory, running service, or web application accessible on the network. Common installation paths: C:\Program Files\Marvell\QConvergeConsole\ or /opt/marvell/qconvergeconsole/. Check for process 'QConvergeConsole' or service 'Marvell QConvergeConsole' running.Affected if QConvergeConsole is installed and running on the system
-
Identify installed versionLocate the version information in the installation directory, typically in a version.txt, about dialog, or the web interface footer. The version may also be visible in the GUI login page or in registry keys under HKLM\Software\Marvell\QConvergeConsole.Affected if Installed version is 5.5.0.85 or lower
-
Verify deleteAppFile endpoint accessibilityAttempt to access the deleteAppFile functionality through the web interface. Look for URLs containing 'deleteAppFile' or similar file deletion operations in the application's API endpoints. Use web proxy or browser developer tools to inspect available requests.Affected if The deleteAppFile method is accessible without authentication
-
Check network exposure of management interfaceDetermine if the QConvergeConsole web management interface is reachable from untrusted networks. Scan for open ports (commonly 8443, 8444, 8080) or check firewall rules and access control lists governing the management interface.Affected if Management interface is exposed to the internet or untrusted networks without VPN/access controls
If QConvergeConsole version is 5.5.0.85 or lower AND the deleteAppFile endpoint is accessible (especially from untrusted networks), the system is vulnerable to unauthenticated arbitrary file deletion via path traversal.
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.
From vendor dataApply vendor-provided patches immediately. If no patch is available, restrict network access to QConvergeConsole management interfaces and implement web application firewall rules to detect and block directory traversal patterns in requests.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6798 — 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-6798 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