dbcve.org
Qsync CentralApplication · Qnap

CVE-2025-48724

HIGH · 8.1 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 5.0.0.4 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) 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 confidence

A buffer overflow vulnerability exists in Qsync Central that allows an authenticated remote attacker with a valid user account to modify memory or crash processes. The vulnerability stems from improper bounds checking when handling input, allowing an attacker to overflow a buffer and potentially execute arbitrary code or cause denial of service.

MitigationUpgrade Qsync Central to version 5.0.0.4 or later. Since the vulnerability requires a valid user account, ensure strong credential policies and consider network segmentation to limit exposure to untrusted users.

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
Qsync CentralApplication
Affected:>= 5.0.0.0, < 5.0.0.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Qsync Central is installed
    Access the QNAP NAS web interface and navigate to App Center, or use the CLI command 'qpkg -i | grep -i qsync' via SSH to list installed QPKG packages.
    Affected if Qsync Central appears in the installed packages list.
  2. Identify the installed Qsync Central version
    In the QNAP web interface, go to App Center > Qsync Central > three-dot menu > Check Update to view the current version. Alternatively, via CLI run 'qpkg -e Qsync_Central -v' or check '/share/CACHEDEV1_DATA/.qpkg/Qsync_Central/.config.ini' for version information.
    Affected if A version number is returned from the query.
  3. Compare version against vulnerable range
    Check if the installed version falls within >= 5.0.0.0 and < 5.0.0.4. The format should be exactly as displayed (for example: 5.0.0.0, 5.0.0.1, 5.0.0.2, or 5.0.0.3).
    Affected if The installed version is 5.0.0.0, 5.0.0.1, 5.0.0.2, or 5.0.0.3.
  4. Confirm Qsync Central service is accessible over network
    Verify that the Qsync Central web interface is accessible on the network (typically ports 443 or 8080 on the NAS). Check if remote users can authenticate to the Qsync service.
    Affected if The Qsync Central web portal is reachable and accepts user authentication.

If Qsync Central version is 5.0.0.0 through 5.0.0.3 and the service is accessible to authenticated users, the environment is affected by CVE-2025-48724.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.0.0.4 or later
Fixed in 5.0.0.4
Interim mitigation

Upgrade Qsync Central to version 5.0.0.4 or later. Since the vulnerability requires a valid user account, ensure strong credential policies and consider network segmentation to limit exposure to untrusted users.

Recommended fix High confidence

Qsync Central 5.0.0.4

  1. 1. Log into the QNAP device running Qsync Central.
  2. 2. Open the Qsync Central application.
  3. 3. Navigate to the Settings or System Administration section.
  4. 4. Check the current Qsync Central version (should be >= 5.0.0.0 and < 5.0.0.4).
  5. 5. Initiate the update to Qsync Central version 5.0.0.4 or later.
  6. 6. Verify the installation completed successfully and the version is now 5.0.0.4 or higher.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qsync Central Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48724 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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