File StationApplication · Qnap

CVE-2025-52865

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-07
Fix available
A fix is available. Upgrade to 5.5.6.5018 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 NULL pointer dereference vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.5018 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 NULL pointer dereference vulnerability in QNAP File Station 5 allows authenticated remote attackers (who first obtain valid user credentials) to trigger a denial-of-service condition by causing the application to crash via dereferencing a null pointer.

MitigationUpdate File Station 5 to version 5.5.6.5018 or later. Since exploitation requires a valid user account, enforce strong password policies and consider enabling multi-factor authentication to reduce the 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.5018

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 File Station 5 is installed
    Access QTS App Center and look for File Station in the installed applications list, or run this command on the QNAP NAS: cat /etc/config/FileStation5/version 2>/dev/null || echo 'Not installed'
    Affected if File Station 5 is not present on the system
  2. Retrieve the installed version of File Station 5
    Run this command on the QNAP NAS: cat /etc/config/FileStation5/version. Alternatively, in QTS App Center, click on File Station and view the version information displayed there.
    Affected if Unable to determine the version number from the system
  3. Compare version against affected range
    Check if the installed version falls within >= 5.5.6.4691 AND < 5.5.6.5018. For example, version 5.5.6.4900 is affected because it is greater than or equal to 5.5.6.4691 and less than 5.5.6.5018.
    Affected if The installed version is 5.5.6.4691 or higher but lower than 5.5.6.5018 (for example, 5.5.6.4691, 5.5.6.4900, or 5.5.6.5017 would all be affected)
  4. Verify user authentication is enabled
    Confirm that local user accounts or domain users exist on the QNAP NAS that can authenticate to File Station. Check via QTS Control Panel > User > User List, or run: getent passwd | grep -v '^$'
    Affected if At least one valid user account exists on the NAS (this is required for the vulnerability to be exploitable)

You are affected if File Station 5 is installed with a version between 5.5.6.4691 and 5.5.6.5017 inclusive, and there is at least one user account that can authenticate to the application.

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.5018 or later
Fixed in 5.5.6.5018
Interim mitigation

Update File Station 5 to version 5.5.6.5018 or later. Since exploitation requires a valid user account, enforce strong password policies and consider enabling multi-factor authentication to reduce the attack surface.

Recommended fix High confidence

File Station 5.5.6.5018

  1. Verify current File Station version in use
  2. Upgrade File Station to version 5.5.6.5018 or later via QNAP's software update mechanism

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-52865 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