CVE-2025-47206
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 · uneditedAn out-of-bounds write vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to modify or corrupt memory. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.4933 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 confidenceAn out-of-bounds write vulnerability in QNAP File Station 5 allows a remote authenticated attacker to write beyond allocated memory boundaries, potentially leading to memory corruption and possible code execution.
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>= 5.5.6.4691, < 5.5.6.4933CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate File Station 5 version in QNAP Admin GUILog into QNAP NAS admin interface, navigate to App Center or Applications > File Station, and find the installed version number displayed.Affected if Version shown is 5.5.6.4691 through 5.5.6.4932 (inclusive)
-
Locate File Station 5 version via QNAP CLIAccess the QNAP NAS via SSH or console, then run: cat /share/CACHEDEV1_DATA/.qpkg/FileStation5/.qpkg_version 2>/dev/null or check /etc/config/qpkg.conf for FileStation5 entry.Affected if Version returned is 5.5.6.4691 through 5.5.6.4932 (inclusive)
-
Confirm File Station 5 is installed and runningRun: ps | grep -i filestation or check the QNAP App Center status to verify File Station 5 is actively installed on the system.Affected if File Station 5 is installed and running with a version in the affected range
You are affected if QNAP File Station 5 is installed with version 5.5.6.4691 or higher but lower than 5.5.6.4933.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.5.6.4933
Update File Station 5 to version 5.5.6.4933 or later. Additionally, enforce strong user account security to prevent attackers from gaining the initial user access required to exploit this vulnerability.
File Station 5 version 5.5.6.4933 or later
- Identify the current installed version of File Station 5 on the QNAP device
- Navigate to the QNAP App Center or File Station settings to check for updates
- Upgrade File Station 5 to version 5.5.6.4933 or later
- Verify the upgrade was successful by confirming the new version number after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-47206 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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