dbcve.org
QtsOperating system · Qnap

CVE-2025-30264

HIGH · 8.8 CVSS v3.1 Published 2025-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 a user account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.2.5.3145 build 20250526 and later QuTS hero h5.2.5.3138 build 20250519 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

Command injection vulnerability in QNAP QTS and QuTS hero operating systems. An authenticated remote attacker who has obtained valid user credentials can inject and execute arbitrary commands on the affected system due to insufficient input validation.

MitigationApply vendor security updates: QTS 5.2.5.3145 build 20250526 or later, QuTS hero h5.2.5.3138 build 20250519 or later. Until patched, restrict network exposure and enforce strong credential policies to reduce the attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed QTS or QuTS hero version
    Log into the QNAP admin console and navigate to Control Panel > System > Firmware Update, or run 'fw_manager --version' via SSH if available. Note the full build number displayed.
    Affected if The version matches any of the listed affected builds: 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.
  2. Confirm the system firmware build number
    In the admin interface, go to Control Panel > System > About > Firmware. Record the exact Build number (for example, 20250526).
    Affected if The build number is earlier than 20250526 for QTS or earlier than 20250519 for QuTS hero.
  3. Determine if remote access services are enabled
    In the admin interface, go to Control Panel > Network & File Services > Telnet/SSH. Check if SSH or Telnet is enabled and accessible from the external network. Also check myQNAPcloud DDNS settings.
    Affected if SSH or other remote management interfaces are exposed to the internet or untrusted networks.
  4. Review user accounts for compromised credentials
    Go to Control Panel > User & Group > User List. Check for any unfamiliar users, recently added accounts, or accounts with elevated privileges that were not created by an administrator.
    Affected if Unknown or unauthorized user accounts exist on the system.

The system is affected if it runs any of the specific QTS or QuTS hero versions listed and has network-accessible management interfaces that could be reached by an attacker with valid credentials.

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 vendor security updates: QTS 5.2.5.3145 build 20250526 or later, QuTS hero h5.2.5.3138 build 20250519 or later. Until patched, restrict network exposure and enforce strong credential policies to reduce the attack surface.

Recommended fix High confidence

QTS 5.2.5.3145 (build 20250526) or later; QuTS hero h5.2.5.3138 (build 20250519) or later

  1. 1. Identify the current QNAP device model and determine if it runs QTS or QuTS hero firmware
  2. 2. Check the current firmware version (Control Panel > System > Firmware Update or via Qfinder Pro)
  3. 3. If running an affected QTS version (5.2.0.2737, 5.2.0.2744, 5.2.0.2782, or 5.2.0.2802), initiate firmware update
  4. 4. If running an affected QuTS hero version (h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, or h5.2.0.2802), initiate firmware update
  5. 5. Use the built-in QNAP firmware update mechanism to install the latest available version
  6. 6. Verify the installed version meets or exceeds QTS 5.2.5.3145 (build 20250526) for QTS devices or QuTS hero h5.2.5.3138 (build 20250519) for QuTS hero devices
  7. 7. Confirm the vulnerability is remediated by verifying the firmware version
Caveat Standard QNAP firmware upgrade risks apply - ensure data is backed up before updating

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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