dbcve.org
QconvergeconsoleApplication · Marvell

CVE-2025-6795

HIGH · 7.5 CVSS v3.1 Published 2025-07-07
Fix available
A fix is available. Upgrade to after 5.5.0.85 or later.
See remediation →
84/100
Remediation priority · High
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
Marvell QConvergeConsole getFileUploadSize Directory Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Marvell QConvergeConsole. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the getFileUploadSize 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 disclose information in the context of SYSTEM. Was ZDI-CAN-24914.

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 confidence

This is a directory traversal vulnerability in Marvell QConvergeConsole's getFileUploadSize method. The method lacks proper validation of user-supplied paths before using them in file operations, allowing unauthenticated remote attackers to access sensitive files on the system. The vulnerability exposes information in the context of SYSTEM privileges.

MitigationApply the vendor patch when available. In the interim, restrict network access to QConvergeConsole management interfaces and implement Web Application Firewall rules to detect directory traversal patterns in requests.

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
QconvergeconsoleApplication
Affected:<= 5.5.0.85

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Verify QConvergeConsole is installed
    Locate the QConvergeConsole installation directory, typically found under the Marvell or QConvergeConsole program folders on Windows, or /opt/marvell/qconvergeconsole on Linux. Check for the presence of the main application executable (QConvergeConsoleGUI.exe or equivalent) and the web application components.
    Affected if The application is present on the system and the web interface is accessible.
  2. Determine installed version
    Open the QConvergeConsole application and navigate to the About or Help section to view the software version. Alternatively, check the installation logs or version file in the application directory for the exact version number.
    Affected if The installed version is 5.5.0.85 or any version lower than 5.5.0.85, since the vulnerability affects versions up to and including 5.5.0.85.
  3. Confirm web interface is accessible
    Attempt to access the QConvergeConsole web portal via browser at the default ports (typically 8443 or 8080 for HTTPS, or check your specific deployment). Verify the service is running by accessing the login page or API endpoint.
    Affected if The QConvergeConsole web interface is reachable over the network, making the vulnerable endpoint potentially exploitable.
  4. Identify exposure to unauthenticated network access
    Review firewall rules and network access controls to determine if the QConvergeConsole web port is exposed to untrusted networks or the public internet. Check whether authentication is required to reach the application.
    Affected if The web interface is accessible without authentication from untrusted networks, allowing unauthenticated attackers to reach the vulnerable getFileUploadSize method.
  5. Inspect HTTP access logs for traversal patterns
    Examine the QConvergeConsole web server access logs (typically stored in the logs directory within the installation folder) for requests to the getFileUploadSize endpoint that contain directory traversal sequences such as ../, ..\, or absolute path patterns.
    Affected if Evidence exists in logs of directory traversal requests targeting the getFileUploadSize method, indicating exploitation attempts or successful access.

A system is affected if QConvergeConsole version 5.5.0.85 or lower is installed with its web interface accessible to unauthenticated network users.

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.

From vendor data
Upgrade available Upgrade to a release after 5.5.0.85
Interim mitigation

Apply the vendor patch when available. In the interim, restrict network access to QConvergeConsole management interfaces and implement Web Application Firewall rules to detect directory traversal patterns in requests.

Fix this in Qconvergeconsole Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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