dbcve.org
QtsOperating system · Qnap

CVE-2023-47568

HIGH · 8.8 CVSS v3.1 Published 2024-02-02
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 SQL injection vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow authenticated users to inject malicious code via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.5.2645 build 20240116 and later QTS 4.5.4.2627 build 20231225 and later QuTS hero h5.1.5.2647 build 20240118 and later QuTS hero h4.5.4.2626 build 20231225 and later QuTScloud c5.1.5.2651 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

SQL injection vulnerability in QNAP QTS, QuTS hero, and QuTScloud operating systems allows authenticated users to inject malicious SQL code via network requests. The vulnerability exists in multiple legacy versions prior to the patched builds released in December 2023/January 2024.

MitigationApply the appropriate firmware update for the installed QNAP operating system version (QTS 5.1.5.2645+, QTS 4.5.4.2627+, QuTS hero h5.1.5.2647+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+) 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:= 4.5.4.1715= 4.5.4.1723= 4.5.4.1741= 4.5.4.1787= 4.5.4.1800= 4.5.4.1892= 4.5.4.1931= 4.5.4.2012= 4.5.4.2117= 4.5.4.2280= 4.5.4.2374= 4.5.4.2627
Quts HeroOperating system
Affected:= h4.5.4.1771= h4.5.4.1800= h4.5.4.1813= h4.5.4.1848= h4.5.4.1892= h4.5.4.1951= h4.5.4.1971= h4.5.4.1991= h4.5.4.2052= h4.5.4.2138= h4.5.4.2217= h4.5.4.2272
QutscloudOperating system
Affected:= c5.1.0.2498

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 QNAP operating system and version
    Log into the QNAP admin console and navigate to Control Panel > System > Firmware Update, or use the command 'getsysinfo' via SSH to retrieve the exact firmware version string (e.g., 4.5.4.1931 or h4.5.4.1991)
    Affected if The displayed version matches any of the affected versions: QTS = 4.5.4.1715, 1723, 1741, 1787, 1800, 1892, 1931, 2012, 2117, 2280, 2374, 2627; QuTS hero = h4.5.4.1771, 1800, 1813, 1848, 1892, 1951, 1971, 1991, 2052, 2138, 2217, 2272; QuTScloud = c5.1.0.2498
  2. Confirm the device is accessible with admin credentials
    Verify that valid administrator credentials exist for the QNAP device (either local account or domain account). The vulnerability requires an authenticated session to inject SQL code.
    Affected if Admin access is present and the version from step 1 is in the affected list above
  3. Verify the firmware is not on a patched build
    Compare your installed version against the minimum patched builds: QTS 4.5.4.2627 or later, QTS 5.1.5.2645 or later; QuTS hero h4.5.4.2626 or later, h5.1.5.2647 or later; QuTScloud c5.1.5.2651 or later
    Affected if Your version is below these patched build numbers and appears in the affected version list

You are affected if your QNAP device runs any version listed as affected and you have admin authentication capability; you are not affected if your firmware version matches or exceeds the patched build numbers.

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 appropriate firmware update for the installed QNAP operating system version (QTS 5.1.5.2645+, QTS 4.5.4.2627+, QuTS hero h5.1.5.2647+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+) to remediate this vulnerability.

Recommended fix High confidence

Upgrade to QTS 4.5.4.2627+ or QTS 5.1.5.2645+ (depending on branch); QuTS hero h4.5.4.2626+ or h5.1.5.2647+; or QuTScloud c5.1.5.2651+

  1. 1. Identify the specific QNAP product (QTS, QuTS hero, or QuTScloud) and current version installed on the device
  2. 2. For QTS users: If running version 4.5.4.x, upgrade to QTS 4.5.4.2627 build 20231225 or later. If running version 5.x, upgrade to QTS 5.1.5.2645 build 20240116 or later
  3. 3. For QuTS hero users: If running version h4.5.4.x, upgrade to QuTS hero h4.5.4.2626 build 20231225 or later. If running version h5.1.x, upgrade to QuTS hero h5.1.5.2647 build 20240118 or later
  4. 4. For QuTScloud users: Upgrade to QuTScloud c5.1.5.2651 or later
  5. 5. After upgrade, verify the system is functioning normally and confirm the new version is running
Caveat Review QNAP release notes for the target version to check for any compatibility issues or data migration requirements before upgrading

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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