Cyber Resilience

CVE-2025-57707

Qnap File Station 5.5.6.4691 – 5.5.6.5190

Published
11 February 2026
Modified
12 February 2026
Patch / advisory
View advisory
CVSS Score v4 1.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0066 48th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2025-57707 is a low-severity Static Code Injection (CWE-96) vulnerability in Qnap File Station. Its CVSS base score is 1.1 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-57707 is an improper neutralization of directives in statically saved code vulnerability, classified as Static Code Injection (CWE-96), affecting File Station 5 in QNAP devices. Published on 2026-02-11, it carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), highlighting its high severity due to significant impacts on confidentiality, integrity, and availability.

A remote attacker who has obtained a user account on the affected system can exploit this vulnerability over the network with low attack complexity and no user interaction. Exploitation enables the attacker to access restricted data and files that would otherwise be unavailable to their privilege level.

QNAP's security advisory (QSA-26-03) confirms the vulnerability has been fixed in File Station 5 version 5.5.6.5166 and later. Administrators should update to a patched version and consult https://www.qnap.com/en/security-advisory/qsa-26-03 for full mitigation guidance.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

An improper neutralization of directives in statically saved code ('Static Code Injection') vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to access restricted data /…

more

files. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.5166 and later

CWE(s)
CWE-96

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1027.009 Embedded Payloads Stealth
Adversaries may embed payloads within other files to conceal malicious content from defenses.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-57706Same product: Qnap File Station
CVE-2026-26241Same product: Qnap File Station
CVE-2025-29876Same product: Qnap File Station
CVE-2025-54169Same product: Qnap File Station
CVE-2025-29890Same product: Qnap File Station
CVE-2025-29872Same product: Qnap File Station
CVE-2025-62854Same product: Qnap File Station
CVE-2025-53410Same product: Qnap File Station
CVE-2025-22490Same product: Qnap File Station
CVE-2025-29888Same product: Qnap File Station

Affected Assets

qnap
file station
5.5.6.4691 — 5.5.6.5190

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing neutralization of directives in saved code artifacts.

SI-10 Information Input Validation good match

Input validation directly stops unneutralized directives from being inserted into static code resources.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles include secure input handling and neutralization requirements that structurally avoid static injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization to block static code injection into templates, configs, or libraries.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance will detect static code injection but does not prevent it at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents static code injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing untrusted input before it is stored in executable resources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe the specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.

A.8.32 Change management none match
mitigates

Change management can catch unsafe code changes but does not enforce input neutralization.

References