CVE-2025-29875
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 · uneditedA 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.4907 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 confidenceA NULL pointer dereference vulnerability in QNAP File Station 5 allows an authenticated remote attacker to cause a denial-of-service condition. The attacker must first obtain valid user credentials before exploiting the NULL pointer dereference to crash the application.
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.4907CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm QNAP File Station is installedLog into the QNAP NAS admin interface and navigate to App Center or check if File Station appears in the available applicationsAffected if File Station is not listed or not installed means not affected by this CVE
-
Locate the installed File Station versionIn the QNAP admin interface, go to App Center > File Station > click the menu icon (three dots) and select 'About' to view the version numberAffected if The displayed version falls within the range 5.5.6.4691 through 5.5.6.4906, meaning the installation is vulnerable
-
Verify the exact version stringRecord the full version number displayed (for example: 5.5.6.4691, 5.5.6.4700, or 5.5.6.4907)Affected if Version is less than 5.5.6.4907 (versions 5.5.6.4691 through 5.5.6.4906 are affected)
-
Check network exposure of File StationConfirm whether the QNAP NAS web interface (port 8080 or 443) is accessible from network segments where untrusted users could obtain credentialsAffected if The service is exposed to untrusted users who could obtain valid credentials and exploit the NULL pointer dereference
The environment is affected if QNAP File Station is installed and the running version is between 5.5.6.4691 and 5.5.6.4906 inclusive.
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.4907
Update File Station to version 5.5.6.4907 or later. Ensure user account security to prevent unauthorized access that could precede exploitation.
File Station 5 version 5.5.6.4907 or later
- Verify current File Station version by accessing QTS Control Panel > Apps > File Station
- Download File Station 5 version 5.5.6.4907 or later from the QNAP App Center or QNAP website
- Install or update File Station to the fixed version through the QTS interface
- Restart File Station if prompted and verify the new version is installed correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29875 — 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-29875 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