What is the CVSS score of CVE-2025-57707?

CVE-2025-57707 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2025-57707?

Within 24 hours: Identify all File Station 5 deployments and audit active user accounts for suspicious access patterns. Within 7 days: Implement network segmentation to restrict File Station access to authorized personnel only, enforce multi-factor authentication for all File Station accounts, and disable remote access where operationally feasible. Within 30 days: Prepare for vendor patch deployment, conduct full access logs review for unauthorized file access, and consider migration to alternative solutions if patch timeline is unacceptable.

File Station CVE-2025-57707

HIGH

Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') (CWE-96)

2026-02-11 security@qnapsecurity.com.tw

Qnap Code Injection File Station

8.8

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-96 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Static code injection prevention
Impact	CVSS 8.8 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: Low. User interaction: None. Exploitable via remote/network.
Exploit ScenarioDerived	A remote attacker could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

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 / files. [CVSS 8.8 HIGH]

RemediationAI

Monitor vendor advisories for a patch. Restrict network access to the affected service where possible.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Affects File Station. 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 / files.

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

Know when File Station gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

CVE-2025-57707 is a critical vulnerability in File Station 5 that allows authenticated attackers to bypass access controls and access restricted data through static code injection. This poses an immediate risk to organizations storing sensitive information in File Station, as any compromised user account can be leveraged to exfiltrate confidential files regardless of intended access restrictions.

Business Impact: High

Compensating Controls

Implement Web Application Firewall (WAF) rules to block suspicious code injection patterns in File Station requests; enforce strict network segmentation limiting File Station access to trusted IP ranges; enable and monitor audit logging for all file access and account activities; disable File Station's remote access features if not operationally critical; enforce principle of least privilege on all user accounts; conduct daily access log reviews for anomalies. Monitor vendor advisories for patch availability given current lack of fix.

Threat Intelligence Overview

EPSS Score

0.0%

Top 85% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +44

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.