dbcve.org
File StationApplication · Qnap

CVE-2025-57707

HIGH · 8.8 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 5.5.6.5190 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An improper neutralization of directives in statically saved code ('Static Code Injection') vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to access restricted data / files. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.5166 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

This is a static code injection vulnerability in QNAP File Station 5 where improperly neutralized directives in statically saved code allow a remote attacker with a valid user account to inject malicious code and access restricted files/data beyond their intended permissions.

MitigationEnsure all user accounts have strong, unique passwords to prevent account compromise, and upgrade to File Station 5.5.6.5166 or later. Additionally, apply network segmentation and least-privilege user permissions to reduce attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm QNAP File Station 5 installation and version
    Access the QNAP admin interface, navigate to App Center, locate File Station, and note the installed version number. Alternatively, access the device via SSH and run: 'qpkg --get_file_station_version' or check '/etc/config/qpkg.conf' for File Station version entry.
    Affected if The installed version is 5.5.6.4691 or higher but lower than 5.5.6.5190
  2. Verify user authentication is enabled for File Station
    In QNAP admin interface, go to Control Panel > Security > User Account or File Station settings to confirm local or domain user authentication is configured and active.
    Affected if User authentication is enabled with valid user accounts that could be compromised or brute-forced
  3. Confirm remote access to File Station web interface
    Check if File Station is accessible via web browser using the QNAP IP/hostname from a network location. Review QNAP myQNAPcloud settings or router port forwarding rules that may expose the File Station web portal externally.
    Affected if File Station web interface is accessible from outside the local network or from untrusted network segments

Your environment is affected if QNAP File Station 5 is installed with version 5.5.6.4691 through 5.5.6.5189 and is accessible to an attacker who can obtain valid user credentials.

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

Ensure all user accounts have strong, unique passwords to prevent account compromise, and upgrade to File Station 5.5.6.5166 or later. Additionally, apply network segmentation and least-privilege user permissions to reduce attack surface.

Recommended fix High confidence

File Station 5 version 5.5.6.5166 or later

  1. 1. Log in to your QNAP NAS admin interface
  2. 2. Navigate to App Center or File Station settings
  3. 3. Check current File Station version (should be visible in App Center or File Station details)
  4. 4. If version is between 5.5.6.4691 and 5.5.6.5190, update to latest available version
  5. 5. Go to App Center > File Station > Update to install version 5.5.6.5166 or later
  6. 6. Verify the update was successful by checking the installed version number
Caveat Standard QNAP firmware update precautions apply - ensure backups exist before updating

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

Fix this in File Station Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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