dbcve.org
File StationApplication · Qnap

CVE-2025-29872

HIGH · 7.5 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to 5.5.6.4847 or later.
See remediation →
84/100
Remediation priority · High
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
An allocation of resources without limits or throttling vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to prevent other systems, applications, or processes from accessing the same type of resource. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.4847 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

This is a resource exhaustion vulnerability in QNAP File Station 5 where the application fails to properly limit or throttle resource allocation. A remote attacker who has obtained valid user credentials can exploit this to consume excessive system resources, thereby preventing other legitimate users or processes from accessing the same resources - essentially causing a denial-of-service condition.

MitigationUpgrade to File Station 5 version 5.5.6.4847 or later. Additionally, limit user account exposure through network access controls and enforce strong authentication to reduce the likelihood of 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.4847

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the QNAP admin interface (http://QNAP_IP:8080 or https://QNAP_IP:8081), navigate to App Center or the File Station settings to verify the application is installed and running.
    Affected if File Station 5 is present on the system
  2. Locate the installed File Station version
    In the QNAP admin interface, go to App Center, find File Station in the installed applications list, and note the version number displayed.
    Affected if Version shown is 5.5.6.4691 or higher, but lower than 5.5.6.4847
  3. Compare version against affected range
    Review the version number obtained from the App Center. The affected range is any version from 5.5.6.4691 up to but not including 5.5.6.4847.
    Affected if Installed version falls within >= 5.5.6.4691 and < 5.5.6.4847
  4. Verify if user authentication is enabled
    Check File Station settings or QNAP Control Panel under User Accounts to confirm that local or domain user authentication is configured and enabled.
    Affected if User authentication is active, allowing remote attackers with valid credentials to attempt exploitation

The system is affected if File Station 5 version is 5.5.6.4691 or higher but below 5.5.6.4847 and user accounts are accessible for authentication.

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.4847 or later
Fixed in 5.5.6.4847
Interim mitigation

Upgrade to File Station 5 version 5.5.6.4847 or later. Additionally, limit user account exposure through network access controls and enforce strong authentication to reduce the likelihood of credential compromise.

Recommended fix High confidence

File Station 5 version 5.5.6.4847 or later

  1. 1. Identify the QNAP NAS device running File Station 5
  2. 2. Check the current File Station version (v5.5.6.4691 through v5.5.6.4846 is vulnerable)
  3. 3. Access the QNAP Admin Console and navigate to App Center or File Station settings
  4. 4. Update File Station to version 5.5.6.4847 or later to remediate the vulnerability
  5. 5. Verify the update was successful by checking the installed File Station version

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