dbcve.org
File StationApplication · Qnap

CVE-2025-66278

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 5.5.6.5190 or later.
See remediation →
71/100
Remediation priority · Elevated
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 File Station 5. If a remote attacker gains a user 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: File Station 5 5.5.6.5190 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 · moderate confidence

A path traversal vulnerability in QNAP File Station 5 allows authenticated remote attackers to escape the intended directory and read arbitrary files on the system by manipulating file path inputs. An attacker must first compromise valid user credentials to exploit this vulnerability.

MitigationUpgrade File Station 5 to version 5.5.6.5190 or later. Additionally, enforce strong password policies, implement multi-factor authentication, and limit user account privileges to reduce the likelihood of initial credential compromise.

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
File StationApplication
Affected:>= 5.5.6.4691, < 5.5.6.5190

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm File Station 5 is installed
    Access QNAP NAS admin console, navigate to App Center or run 'ls /share/Web/filestation' via SSH to verify File Station 5 is present
    Affected if File Station 5 is not installed, the system is not affected by this specific vulnerability
  2. Identify installed File Station version
    In QNAP admin console, go to App Center > File Station > click the version number, or run 'cat /etc/config/fileStation/app_version' via SSH
    Affected if Installed version falls within >= 5.5.6.4691 and < 5.5.6.5190, meaning the version is vulnerable
  3. Verify remote access is enabled
    Check File Station settings: log into admin console, go to File Station > Settings > General, confirm 'Enable File Station' and remote access features are turned on
    Affected if Remote access to File Station is enabled and exposed to network, creating attack surface
  4. Review user access permissions
    In File Station Settings > Permission, examine which users or groups have access to File Station and their privilege levels
    Affected if Users with File Station access exist, as valid credentials are required for exploitation

System is affected if File Station 5 version is between 5.5.6.4691 and 5.5.6.5190 and remote authenticated access to File Station is enabled.

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
Upgrade available Upgrade to 5.5.6.5190 or later
Fixed in 5.5.6.5190
Interim mitigation

Upgrade File Station 5 to version 5.5.6.5190 or later. Additionally, enforce strong password policies, implement multi-factor authentication, and limit user account privileges to reduce the likelihood of initial credential compromise.

Recommended fix High confidence

File Station 5.5.6.5190 or later

  1. 1. Log into the QNAP NAS admin interface.
  2. 2. Navigate to File Station application.
  3. 3. Check the current File Station version (typically in App Center or within File Station settings).
  4. 4. Verify if the installed version is >= 5.5.6.4691 and < 5.5.6.5190 (affected range).
  5. 5. If affected, update File Station to version 5.5.6.5190 or later via QNAP App Center or QNAP software update mechanism.
  6. 6. After upgrade, verify the new version is 5.5.6.5190 or higher.
Caveat Review QNAP release notes for any compatibility requirements or known issues before upgrading

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

Fix this in File Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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