dbcve.org
QtsOperating system · Qnap

CVE-2025-62849

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 SQL injection vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to execute unauthorized code or commands. 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 · moderate confidence

A critical SQL injection vulnerability in QNAP QTS and QuTS hero operating systems allows remote attackers to execute unauthorized code or commands via specially crafted SQL queries. The vulnerability stems from improper input validation in the affected QNAP firmware versions, enabling attackers to bypass authentication and inject malicious SQL statements.

MitigationUpdate affected QNAP devices to 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 versions to remediate this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 QNAP firmware product type
    Access the QNAP admin web interface and check the System Information page, or run 'getsysinfo' command via SSH to determine if the device runs QTS or QuTS hero
    Affected if The device runs QTS or QuTS hero firmware
  2. Check QTS firmware version
    In QTS admin interface, go to Control Panel > System > Firmware Update > System Information to view the exact version and build number. Alternatively, run 'cat /proc/version' or check the About page in the system settings
    Affected if The QTS 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 QuTS hero firmware version
    In QuTS hero admin interface, navigate to Control Panel > System > Firmware Update > System Information to view the exact version and build number. Alternatively, access via SSH and run 'getsysinfo' or check the firmware version file
    Affected if The QuTS hero 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 network accessibility of admin interface
    Confirm the QNAP admin web interface (typically ports 8080 or 443) is accessible from the network. The SQL injection vulnerability is exploitable remotely via the web application
    Affected if The QNAP admin interface is exposed on the network

A QNAP device running any of the listed QTS or QuTS hero versions with an accessible admin interface is vulnerable to CVE-2025-62849

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

Update affected QNAP devices to 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 versions to remediate this vulnerability.

Recommended fix High confidence

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

  1. 1. Identify the current QNAP OS version by logging into the QNAP admin interface and checking System Settings > System > About
  2. 2. Determine if the device is running QTS or QuTS hero based on the current version number
  3. 3. Back up all critical data and configurations before performing the upgrade
  4. 4. For QTS users: upgrade to QTS 5.2.7.3297 build 20251024 or later
  5. 5. For QuTS hero users: upgrade to either QuTS hero h5.2.7.3297 build 20251024 or later, OR QuTS hero h5.3.1.3292 build 20251024 or later
  6. 6. Verify the upgrade was successful by checking the new firmware version in System > About
Caveat Standard QNAP upgrade precautions apply (backup data, ensure stable power); no specific breaking changes noted in advisory

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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