dbcve.org
Qsync CentralApplication · Qnap

CVE-2025-22482

HIGH · 8.1 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to 4.5.0.6 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 use of externally-controlled format string vulnerability has been reported to affect Qsync Central. If exploited, the vulnerability could allow remote attackers who have gained user access to obtain secret data or modify memory. We have already fixed the vulnerability in the following version: Qsync Central 4.5.0.6 ( 2025/03/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

This is a format string vulnerability in Qsync Central where user-supplied input is used directly as a format string parameter instead of being treated as data. Attackers who have obtained valid user credentials can exploit this to read stack values (via %x, %s specifiers) to leak sensitive data or potentially write to memory locations to modify program execution.

MitigationUpdate Qsync Central to version 4.5.0.6 or later. Until then, enforce strict access controls and limit Qsync Central to trusted users only, as authentication is required for exploitation.

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:>= 4.5.0.3, < 4.5.0.6

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
High
Integrity
High
Availability
None

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

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
    Check for Qsync Central process or installation on the QNAP system. This may be done via the QNAP App Center, command line (ps aux | grep -i qsync), or checking the /share folder for Qsync installations.
    Affected if Qsync Central is not installed on the system.
  2. Determine installed Qsync Central version
    Access QNAP App Center and view the installed version of Qsync Central, or use the QNAP CLI if available to query the package version.
    Affected if Unable to confirm the version number from available sources.
  3. Compare version against vulnerable range
    Check if the installed version falls within >= 4.5.0.3 and < 4.5.0.6. Versions 4.5.0.3, 4.5.0.4, and 4.5.0.5 are vulnerable. Version 4.5.0.6 and later are fixed.
    Affected if The installed version is 4.5.0.3, 4.5.0.4, or 4.5.0.5.
  4. Verify Qsync Central network accessibility
    Confirm whether Qsync Central is exposed to untrusted networks. Check firewall rules, port forwarding, or VPN settings that control access to the Qsync Central web interface or sync ports.
    Affected if Qsync Central is accessible from untrusted networks without proper network segmentation.
  5. Assess authentication exposure
    Determine if user accounts with Qsync Central access are limited to trusted personnel only, since valid credentials are required for exploitation.
    Affected if Qsync Central credentials are distributed to untrusted users or the account pool is large and not closely managed.

The environment is affected if Qsync Central version 4.5.0.3, 4.5.0.4, or 4.5.0.5 is installed and attackers could obtain valid user credentials to reach the application.

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 4.5.0.6 or later
Fixed in 4.5.0.6
Interim mitigation

Update Qsync Central to version 4.5.0.6 or later. Until then, enforce strict access controls and limit Qsync Central to trusted users only, as authentication is required for exploitation.

Recommended fix High confidence

Qsync Central 4.5.0.6

  1. 1. Log in to the QNAP NAS admin interface.
  2. 2. Navigate to the Qsync Central application settings.
  3. 3. Check the current version to confirm it is between 4.5.0.3 and 4.5.0.5 (inclusive).
  4. 4. Access the QNAP App Center or Qsync Central update mechanism.
  5. 5. Check for and install the available update to Qsync Central 4.5.0.6 or later.
  6. 6. Verify the installation was successful by confirming the running version is 4.5.0.6 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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22482 — 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-22482 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