dbcve.org
QtsOperating system · Qnap

CVE-2025-62847

HIGH · 7.5 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An improper neutralization of argument delimiters in a command vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to alter execution logic. We have already fixed the vulnerability in the following versions: QTS 5.2.7.3297 build 20251024 and later QuTS hero h5.2.7.3297 build 20251024 and later QuTS hero h5.3.1.3292 build 20251024 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 · high confidence

This is a command injection vulnerability where improper neutralization of argument delimiters allows remote attackers to alter execution logic by injecting malicious arguments into system commands. The flaw affects multiple QNAP NAS operating system versions and is exploitable remotely without requiring authentication in some attack scenarios.

MitigationUpgrade QNAP systems to the fixed versions (QTS 5.2.7.3297 build 20251024, QuTS hero h5.2.7.3297 build 20251024, or QuTS hero h5.3.1.3292 build 20251024) or later. If immediate patching is not possible, restrict network access to management interfaces and monitor for suspicious command patterns.

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
QtsOperating system
Affected:= 5.2.0.2737= 5.2.0.2744= 5.2.0.2782= 5.2.0.2802= 5.2.0.2823= 5.2.0.2851= 5.2.0.2860= 5.2.1.2930= 5.2.2.2950= 5.2.3.3006= 5.2.4.3070= 5.2.4.3079
Quts HeroOperating system
Affected:= h5.2.0.2737= h5.2.0.2782= h5.2.0.2789= h5.2.0.2802= h5.2.0.2823= h5.2.0.2851= h5.2.0.2860= h5.2.1.2929= h5.2.1.2940= h5.2.2.2952= h5.2.3.3006= h5.2.4.3070

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify the QNAP OS version
    Log into the QNAP admin console and navigate to Control Panel > System > Firmware Update, or run 'lsid' via SSH to retrieve the exact firmware version and build number
    Affected if The displayed version matches any of: QTS 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, 5.2.0.2802, 5.2.0.2823, 5.2.0.2851, 5.2.0.2860, 5.2.1.2930, 5.2.2.2950, 5.2.3.3006, 5.2.4.3070, 5.2.4.3079 OR QuTS Hero h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, h5.2.0.2802, h5.2.0.2823, h5.2.0.2851, h5.2.0.2860, h5.2.1.2929
  2. Confirm the product type
    In the QNAP admin interface, check System > Control Panel > System Settings > About > System Information to verify whether the system is running QTS or QuTS Hero
    Affected if The system is running either QTS or QuTS Hero and the version matches the affected list in step 1
  3. Determine remote management exposure
    Check if the QNAP web administration interface (ports 8080, 8081, 443) is accessible from the internet or untrusted networks by reviewing firewall rules or running an external port scan
    Affected if The management interface is exposed to untrusted networks without VPN or IP-based access controls
  4. Audit for suspicious processes or command injection artifacts
    Review system logs in Log Center for unusual commands, unexpected shell executions, or signs of payload injection. Check running processes for unknown executables spawned from web server contexts
    Affected if Unfamiliar processes are running or logs show unexpected command executions with injected delimiters or arguments

The environment is affected if the QNAP system runs QTS or QuTS Hero versions matching those listed in the affected versions and the management interface is network-accessible to potential attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade QNAP systems to the fixed versions (QTS 5.2.7.3297 build 20251024, QuTS hero h5.2.7.3297 build 20251024, or QuTS hero h5.3.1.3292 build 20251024) or later. If immediate patching is not possible, restrict network access to management interfaces and monitor for suspicious command patterns.

Recommended fix High confidence

QTS 5.2.7.3297 build 20251024 or later; QuTS hero h5.2.7.3297 build 20251024 or later; or QuTS hero h5.3.1.3292 build 20251024 or later

  1. 1. Log into the QNAP admin interface (QTS or QuTS hero).
  2. 2. Navigate to Control Panel > System > Firmware Update.
  3. 3. Check the current firmware version to confirm it matches one of the affected versions (5.2.0.2737, 5.2.0.2744, 5.2.0.2782, or 5.2.0.2802 for QTS; h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, or h5.2.0.2802 for QuTS hero).
  4. 4. Create a full system backup of all critical data, as recommended by QNAP best practices before firmware updates.
  5. 5. Initiate the firmware update to check for available updates.
  6. 6. If the fixed version is not offered automatically, manually download the firmware from the QNAP download center for the appropriate model.
  7. 7. Apply QTS version 5.2.7.3297 (build 20251024 or later), or for QuTS hero apply either h5.2.7.3297 (build 20251024 or later) or h5.3.1.3292 (build 20251024 or later).
  8. 8. After the update completes, verify the new firmware version matches one of the fixed releases.
Caveat Standard QNAP firmware update risks apply - ensure backup before upgrading; verify hardware compatibility with new firmware version

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

Fix this in Qts Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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