Skip to main content

Qsync Central CVE-2025-54153

| EUVDEUVD-2025-32440 HIGH
SQL Injection (CWE-89)
2025-10-03 security@qnapsecurity.com.tw
8.6
CVSS 4.0 · Vendor: qnapsecurity
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain valid low-privileged user account
  2. Delivery
    Submit crafted input to vulnerable Qsync Central parameter
  3. Exploit
    Inject SQL into backend query
  4. Execution
    Execute unauthorized database commands
  5. Impact
    Exfiltrate or tamper with stored data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to first possess a valid, even if low-privileged, user account on the targeted Qsync Central installation (CVSS PR:L) - this is the primary limiting factor and rules out anonymous mass exploitation. No user interaction is required (UI:N) and the attack is over the network (AV:N) against the application's standard authenticated interface, so once credentials are held, no special non-default configuration is indicated in the vendor description. Affected deployments are Qsync Central 5.0.0 up to (but not including) 5.0.0.2; upgrading to 5.0.0.2 or later removes the condition. The impact is bounded to confidentiality and integrity of the backend database (VA:N - no availability/denial-of-service effect).

Impact

Multiple signals converge on this being a genuine but second-tier priority rather than an emergency. The QNAP-assigned CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) scoring 8.6 indicates remote, low-complexity exploitation requiring only a low-privileged authenticated user account, with high confidentiality and integrity impact (VC:H/VI:H) but no availability impact (VA:N) and no scope change to subsequent systems. The PR:L requirement is the single most important mitigating factor: an attacker must first obtain a valid user account, which contradicts a mass-exploitation profile. This is corroborated by the EPSS score of just 0.09% (26th percentile), signalling very low predicted exploitation probability. There is no CISA KEV listing and no public proof-of-concept referenced in the provided data, so exploitation is not confirmed in the wild. The signals are internally consistent - there is no CVSS-versus-description conflict - but note the description's phrasing 'execute unauthorized code or commands' slightly overstates a CWE-89 SQL injection, which the vector more accurately scopes to data confidentiality/integrity (VA:N, no availability loss), so treat claims of full code execution with caution pending vendor clarification. Overall: a legitimately high-severity authenticated SQLi worth patching on a normal cycle, not a drop-everything zero-day.

Exploit ScenarioDerived

An attacker who has obtained or been granted a low-privileged account on a QNAP NAS running Qsync Central sends crafted input to a vulnerable parameter, injecting SQL that is executed by the backend database. This lets them read or tamper with data beyond their authorization level and, per the vendor, potentially influence command execution. No public exploit code is identified at time of analysis, and exploitation is gated by first needing valid credentials.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv2 – Oct 18, 2026

SQL injection in QNAP Qsync Central 5.0.0 (all builds prior to 5.0.0.2) allows a remote attacker who already holds a valid, even low-privileged, user account to inject arbitrary SQL through the application's standard network interface, resulting in full compromise of the confidentiality and integrity of the backend database - potentially escalating to unauthorized code or command execution as the vendor notes. The vulnerability is not known to be actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis; EPSS is 0.09% (26th percentile), reflecting the mitigating requirement for valid credentials (CVSS v3.1 PR:L, AV:N, AC:L, UI:N). QNAP has released a fixed build, 5.0.0.2 (2025/07/31), which should be applied to eliminate the condition.

Earlier versions of this analysis (1)
v1 Mar 13, 2026 - 19:29 CVSS 8.8

RemediationAI

Vendor-released patch: Qsync Central 5.0.0.2 (released 2025/07/31) and later. Upgrade via QNAP App Center (or the QTS/QuTS hero App Center update notification) to 5.0.0.2 or a newer build, and verify the installed version afterwards; refer to QSA-25-35 at https://www.qnap.com/en/security-advisory/qsa-25-35 for the official version matrix and any prerequisite firmware levels before updating. Because exploitation requires a valid account, the highest-value interim controls are account-side: delete or disable dormant Qsync Central accounts, enforce least privilege so ordinary users cannot reach administrative sync/sharing functions, enable MFA on the NAS, and rotate credentials for any account suspected of compromise - the trade-off is lost convenience for shared or service accounts. Where Qsync Central does not need to be reachable from the internet, restrict the service to trusted internal subnets or VPN-only access via firewall rules on the NAS and perimeter, accepting that roaming sync clients will require VPN connectivity. If the package is unused, stop and uninstall it to remove the attack surface entirely, at the cost of losing sync functionality. Detection-oriented measures such as forwarding Qsync Central and database/HTTP logs to a SIEM and alerting on anomalous SQL error bursts or unusual authenticated requests provide only partial coverage and should not be relied on in place of the 5.0.0.2 upgrade; note that QNAP advisories occasionally report newly disclosed issues against recently patched builds, so subscribe to QNAP security notifications rather than treating this upgrade as a one-time action.

Affected VersionsENISA

Qsync Central 5.0.0 <5.0.0.2 ( 2025/07/31 )

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

The issue is a classic SQL injection (CWE-89) in Qsync Central, QNAP's central file-synchronization and sharing service that runs on QTS/QuTS hero NAS appliances and stores its metadata - accounts, shares, sync folders, job state - in a backend database. User-supplied input reaching a database query is not sufficiently neutralized (improper neutralization of special elements used in an SQL command), so an attacker can alter query logic rather than merely read the records intended by the application. Because the injection point sits on the ordinary authenticated application interface, the attacker must first possess a valid account; the CVSS v3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) confirms a network-reachable, low-complexity, no-user-interaction attack requiring low privileges, with high confidentiality and integrity impact but no availability impact (VA:N), so denial-of-service is neither the goal nor an expected side effect. The vendor's own wording notes that successful exploitation may extend from data manipulation to 'unauthorized code or commands', which is consistent with database-level features (e.g., stacked queries or privileged database functions) being reachable from the injectable context. The CPE string cpe:2.3:a:qnap:qsync_central:*:*:*:*:*:*:*:* is a wildcard entry because the vendor and EUVD enumerate the affected range only as 5.0.0 up to (but not including) 5.0.0.2, i.e. the 5.0.0 branch before the 2025/07/31 rebuild.

Know when Qsync Central 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

No credit card · 7-day full trial

Severity by source

Vendor (qnapsecurity) PRIMARY 8.6 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 8.1 HIGH

Network-reachable authenticated SQLi needing only a low-privileged account, hence AV:N/AC:L/PR:L/UI:N; high confidentiality and integrity impact with no availability loss per CWE-89 and VA:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (qnapsecurity).

CVSS VectorVendor: qnapsecurity

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

5
CVSS changed
Oct 18, 2026 - 21:38 NVD
8.8 (HIGH) 8.6 (HIGH)
Analysis Updated
Apr 16, 2026 - 06:25 EUVD-patch-fix
executive summary
Patch available
Apr 16, 2026 - 05:29 EUVD
5.0.0.2
CVE Published
Oct 03, 2025 - 19:15 cve.org
HIGH 8.6
CVE Published
Oct 03, 2025 - 19:15 nvd
HIGH 8.8

DescriptionCVE.org

An SQL injection vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to execute unauthorized code or commands.

We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.2 ( 2025/07/31 ) and later

Executive ViewAI

Why It Matters

Qsync Central contains a high-severity SQL injection vulnerability (CVSS 8.8) that allows authenticated remote attackers to execute unauthorized code, potentially compromising data integrity and system confidentiality. Organizations using Qsync Central versions prior to 5.0.0.2 face immediate risk of database manipulation and code execution if user accounts are compromised through credential exposure or social engineering.

Business Impact: High
Compensating Controls

Apply vendor patch. Vendor-released patch: Qsync Central 5.0.0.2 (released 2025/07/31) and later. If immediate patching is not feasible, implement network-level access controls to restrict Qsync Central user account creation and limit authentication mechanisms to prevent credential compromise; monitor SQL query logs for injection patterns.

Threat Intelligence Overview

EPSS Score
0.1%
Top 74% exploitable
Prevalence
Medium
QNAP NAS sync-management app; common on SMB/prosumer appliances, not universal
Data Quality
4 sources
Confidence: Medium

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.1%
Patch available Yes
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
No
Human Impact
High

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2025-30276 HIGH
8.8 Feb 11

An out-of-bounds write vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user accoun

CVE-2025-29892 HIGH
8.8 Jun 06

SQL injection vulnerability in Qsync Central that allows authenticated remote attackers to execute arbitrary code or com

CVE-2025-53595 HIGH
8.6 Oct 03

SQL injection in QNAP Qsync Central versions 5.0.0 through below 5.0.0.2 lets a remote attacker who already holds a vali

CVE-2025-30278 HIGH
8.3 Aug 29

An improper certificate validation vulnerability has been reported to affect Qsync Central. Rated high severity (CVSS 8.

CVE-2025-30277 HIGH
8.3 Aug 29

An improper certificate validation vulnerability has been reported to affect Qsync Central. Rated high severity (CVSS 8.

CVE-2025-52869 HIGH
8.1 Feb 11

A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, th

CVE-2025-52868 HIGH
8.1 Feb 11

A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, th

CVE-2025-48724 HIGH
8.1 Feb 11

A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, th

CVE-2025-48723 HIGH
8.1 Feb 11

A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, th

CVE-2025-22482 HIGH
8.1 Jun 06

Format string vulnerability in QNAP Qsync Central that allows authenticated remote attackers to read sensitive data or m

CVE-2025-30269 HIGH
8.1 Feb 11

A use of externally-controlled format string vulnerability has been reported to affect Qsync Central. If a remote attack

CVE-2025-57709 HIGH
8.1 Feb 11

A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, th

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy