dbcve.org
File StationApplication · Qnap

CVE-2026-24724

HIGH · 8.1 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 5.5.6.5243 or later.
See remediation →
87/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
An incorrect authorization vulnerability has been reported to affect File Station 6. If a remote attacker gains a user account, they can then exploit the vulnerability to bypass intended access restrictions. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.5243 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 an incorrect authorization vulnerability in QNAP File Station 6 that allows a remote authenticated attacker to bypass intended access restrictions. The flaw appears to be in the access control logic where proper authorization checks are not enforced, potentially allowing users to access files or directories outside their permitted scope.

MitigationUpgrade to File Station 5 version 5.5.6.5243 or later (or apply the corresponding patch for File Station 6). Since the attacker requires valid user credentials, enforce strong password policies and consider network segmentation to limit exposure.

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.5243

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 is installed
    Access your QNAP NAS admin interface and verify that File Station application is installed and running
    Affected if File Station is not present on the system, the vulnerability does not apply
  2. Identify the installed File Station version
    Navigate to File Station settings or the QNAP App Center to view the installed version number of File Station
    Affected if Unable to determine the version number for comparison
  3. Compare version against affected range
    Check if the installed version is >= 5.5.6.4691 and < 5.5.6.5243
    Affected if The installed version falls within the affected range (>= 5.5.6.4691 and < 5.5.6.5243)
  4. Verify user authentication is enabled
    Confirm that user account authentication is enabled and remote access to File Station is permitted
    Affected if Remote user authentication is enabled, allowing potential attackers with valid credentials to attempt exploitation

You are affected if File Station is installed with a version between 5.5.6.4691 and 5.5.6.5242 inclusive and remote user authentication is accessible.

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.5243 or later
Fixed in 5.5.6.5243
Interim mitigation

Upgrade to File Station 5 version 5.5.6.5243 or later (or apply the corresponding patch for File Station 6). Since the attacker requires valid user credentials, enforce strong password policies and consider network segmentation to limit exposure.

Recommended fix High confidence

File Station 5 version 5.5.6.5243 or later

  1. 1. Identify the current File Station version by accessing the QNAP admin interface and navigating to File Station > Settings > About
  2. 2. If the current version is >= 5.5.6.4691 and < 5.5.6.5243, the installation is vulnerable
  3. 3. Access the QNAP App Center or check www.qnap.com for the File Station 5.5.6.5243 update or later version
  4. 4. Download and install the updated File Station package through the QNAP interface
  5. 5. After installation, verify the version by checking File Station > Settings > About to confirm version 5.5.6.5243 or later is installed
  6. 6. Review user account permissions to ensure no unauthorized accounts were created during the vulnerability window
Caveat Standard firmware/app update precautions apply - ensure backups are current before applying updates

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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