dbcve.org
QtsOperating system · Qnap

CVE-2025-47212

HIGH · 7.2 CVSS v3.1 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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 command injection vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains an administrator account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.2.6.3195 build 20250715 and later QuTS hero h5.2.6.3195 build 20250715 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

Command injection vulnerability in QNAP operating system (QTS and QuTS hero) that allows authenticated remote attackers with administrator privileges to execute arbitrary commands on the underlying system.

MitigationApply the vendor-supplied firmware updates (QTS 5.2.6.3195 build 20250715 or QuTS hero h5.2.6.3195 build 20250715 and later). Since the vulnerability requires administrator access, ensure strong credential policies and consider network segmentation to limit exposure.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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. Identify the QNAP product type
    Log into the QNAP device and navigate to Control Panel > System > System Status, or check the login page/console for the operating system name (QTS or QuTS hero)
    Affected if The device is running QTS or QuTS hero firmware
  2. Check the installed QTS version
    Navigate to Control Panel > System > System Status > Firmware Version, or use the command `getcfg system version` via SSH/CLI
    Affected if The version matches any of: 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, or 5.2.4.3079
  3. Check the installed QuTS hero version
    Navigate to Control Panel > System > System Status > Firmware Version, or use the command `getcfg system version` via SSH/CLI
    Affected if The version matches any of: 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, or h5.2.4.3070
  4. Verify remote administrative access is enabled
    Check Control Panel > System > General Settings > System Administration > Remote Access (or similar) to see if remote administrator login is permitted, or verify the device is accessible from untrusted networks
    Affected if Remote administrator access is enabled and the device is network-accessible to potential attackers

The device is affected if it runs QTS or QuTS hero with any of the listed versions AND has remote administrator access enabled, allowing authenticated remote attackers to inject commands.

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

Apply the vendor-supplied firmware updates (QTS 5.2.6.3195 build 20250715 or QuTS hero h5.2.6.3195 build 20250715 and later). Since the vulnerability requires administrator access, ensure strong credential policies and consider network segmentation to limit exposure.

Recommended fix High confidence

QTS 5.2.6.3195 build 20250715 or later / QuTS hero h5.2.6.3195 build 20250715 or later

  1. 1. Back up all critical data and system configurations before proceeding with the upgrade.
  2. 2. Download the QTS 5.2.6.3195 firmware (build 20250715) or QuTS hero h5.2.6.3195 firmware (build 20250715) from the official QNAP download center at www.qnap.com.
  3. 3. Log in to the QNAP admin console with administrator credentials.
  4. 4. Navigate to Control Panel > System > Firmware Update.
  5. 5. Select 'Manual Firmware Update' and upload the downloaded firmware file.
  6. 6. Confirm the update and wait for the system to reboot automatically.
  7. 7. After the system restarts, verify the firmware version matches 5.2.6.3195 (build 20250715) or later in Control Panel > System > Firmware Update.
  8. 8. Review system logs to ensure the update completed successfully and no anomalous commands were executed.
Caveat Review QNAP release notes for this build for any feature changes or known issues before upgrading production systems

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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