dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-26692

HIGH · 8.1 CVSS v3.0 Published 2025-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Quick Agent V3 and Quick Agent V2 contain an issue with improper limitation of a pathname to a restricted directory ('Path Traversal'). If exploited, arbitrary code may be executed by a remote unauthenticated attacker with the Windows system privilege where the product is running.

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

Quick Agent V2 and V3 contain a path traversal vulnerability that allows remote unauthenticated attackers to access files outside the restricted directory and execute arbitrary code with Windows system privileges.

MitigationImplement strict input validation on file path parameters, use allow-list approaches for permitted paths, and ensure the application runs with least-privilege accounts rather than system privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Quick Agent installation
    Check for Quick Agent V2 or V3 installation by examining installed programs list in Windows Control Panel, or searching for 'Quick Agent' in Program Files directories (typically C:\Program Files\ or C:\Program Files (x86)\). Also check Windows Services for a service named 'Quick Agent' or similar.
    Affected if Quick Agent V2 or V3 software is installed on the system
  2. Determine installed version
    Locate the Quick Agent executable or DLL file (commonly in the installation directory) and right-click to view Properties, then check the Version tab. Alternatively, run 'wmic product get name,version' or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Quick Agent entries.
    Affected if The installed version falls within Quick Agent V2 or V3 family (any version, since specific version ranges were not provided)
  3. Check if remote/file access feature is enabled
    Examine Quick Agent configuration files (typically .ini, .xml, or .json files in the installation directory) for settings related to remote access, file serving, or API endpoints that accept file path parameters. Look for features named 'file transfer', 'file access', 'remote access', or similar.
    Affected if Remote or file access functionality that accepts path parameters is enabled in the configuration
  4. Verify service account privileges
    Open Windows Services (services.msc), find the Quick Agent service, right-click and select Properties, then check the 'Log on as' account. Also examine the service binary path and any configured execution level in the application.
    Affected if The Quick Agent service runs under a Windows system account (LocalSystem, SYSTEM) or an account with elevated privileges rather than a limited user account
  5. Test for accessible path parameter interface
    If Quick Agent exposes a web interface or API, examine listening ports (run 'netstat -an | findstr LISTENING' looking for ports associated with Quick Agent). Check if endpoints accepting file paths are reachable without authentication.
    Affected if The application accepts unauthenticated requests with file path parameters that could be exploited for path traversal

The environment is affected if Quick Agent V2 or V3 is installed, the remote file access feature is enabled, and the service runs with elevated Windows system privileges, allowing an unauthenticated attacker to potentially traverse paths and execute arbitrary code.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on file path parameters, use allow-list approaches for permitted paths, and ensure the application runs with least-privilege accounts rather than system privileges.

Have this fixed 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 help mitigating

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-26692 — 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-26692 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