dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-52861

HIGH · 7.0 CVSS v4.0 Published 2025-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
Remotely reachable 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
A path traversal vulnerability has been reported to affect VioStor. If a remote attacker gains an administrator account, they can then exploit the vulnerability to read the contents of unexpected files or system data. We have already fixed the vulnerability in the following version: VioStor 5.1.6 build 20250621 and later

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

A path traversal vulnerability in VioStor allows authenticated administrators to use specially crafted file path requests to access files outside the intended directory, potentially exposing sensitive system configuration and data files.

MitigationApply VioStor firmware update 5.1.6 build 20250621 or later. Additionally, enforce strong administrator password policies and monitor for suspicious administrative activity to reduce the likelihood of initial account compromise.

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
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify VioStor firmware version
    Access the VioStor admin panel and navigate to System Settings > System Information, or check the login page footer for the firmware build number
    Affected if The installed version is earlier than 5.1.6 build 20250621
  2. Confirm administrator access is enabled
    Check if administrator accounts are created and accessible through the web login interface at the VioStor portal
    Affected if Administrator authentication is possible, providing the attacker the credentials needed to exploit the path traversal
  3. Verify web-based file management feature is active
    Look for file download, backup, or export features in the admin panel under sections like Backup/Restore, File Manager, or System Tools
    Affected if The file management or download module is accessible to authenticated administrators
  4. Check for unauthorized file access attempts in logs
    Review VioStor system logs or web server access logs for unusual requests with directory traversal patterns such as ../ or absolute paths outside the web root
    Affected if Logs show requests containing path traversal sequences from admin accounts accessing unexpected directories
  5. Inspect file system permissions on sensitive directories
    If you have CLI access, verify that the web server process has read access to /etc, /config, or other system directories beyond the intended storage volumes
    Affected if The application user can access system configuration files outside the designated storage area

You are affected if your VioStor firmware version is earlier than 5.1.6 build 20250621 AND administrator authentication is available to exploit the path traversal in file access features.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply VioStor firmware update 5.1.6 build 20250621 or later. Additionally, enforce strong administrator password policies and monitor for suspicious administrative activity to reduce the likelihood of initial account compromise.

Recommended fix Moderate confidence

VioStor 5.1.6 build 20250621

  1. 1. Identify the current VioStor version installed on the QNAP device
  2. 2. Access the QNAP admin console and navigate to VioStor settings
  3. 3. Check if the current version is earlier than VioStor 5.1.6 build 20250621
  4. 4. If vulnerable, download and install VioStor 5.1.6 build 20250621 or later from the official QNAP download center
  5. 5. After upgrade, verify the installation was successful and the version is correct
  6. 6. Review administrator accounts to ensure no unauthorized admin accounts exist
  7. 7. Monitor for any suspicious activity during and after the upgrade
Caveat Review QNAP release notes for any configuration changes or feature modifications between your current version and 5.1.6

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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