dbcve.org
QtsOperating system · Qnap

CVE-2023-23372

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 cross-site scripting (XSS) vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to inject malicious code via a network. We have already fixed the vulnerability in the following versions: QTS 5.0.1.2425 build 20230609 and later QTS 5.1.0.2444 build 20230629 and later QTS 4.5.4.2467 build 20230718 and later QuTS hero h5.1.0.2424 build 20230609 and later QuTS hero h5.0.1.2515 build 20230907 and later QuTS hero h4.5.4.2476 build 20230728 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 cross-site scripting (XSS) vulnerability in QNAP QTS and QuTS hero operating systems allows remote attackers to inject malicious scripts via network requests. The vulnerability exists in multiple versions of the firmware and can be exploited without authentication in certain configurations.

MitigationUpdate affected QNAP devices to the specified fixed versions (QTS 5.0.1.2425+, QTS 5.1.0.2444+, QTS 4.5.4.2467+, QuTS hero h5.1.0.2424+, QuTS hero h5.0.1.2515+, or QuTS hero h4.5.4.2476+) 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.1.0.2348= 5.1.0.2399= 5.1.0.2418= 5.0.1.2034= 5.0.1.2079= 5.0.1.2131= 5.0.1.2137= 5.0.1.2145= 5.0.1.2173= 5.0.1.2194= 5.0.1.2234= 5.0.1.2248
Quts HeroOperating system
Affected:= h5.1.0.2409= h5.0.1.2045= h5.0.1.2192= h5.0.1.2248= h5.0.1.2269= h5.0.1.2277= h5.0.1.2348= h5.0.1.2376= h4.5.4.1771= h4.5.4.1800= h4.5.4.1813= h4.5.4.1848

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 firmware type
    Log into the QNAP device web interface and navigate to Control Panel > System > About, or use SSH and run 'getsysinfo' or 'cat /etc/config/version' to determine if the device runs QTS or QuTS hero.
    Affected if The device runs either QTS or QuTS hero firmware.
  2. Determine the installed QTS version
    In the web interface, go to Control Panel > System > About and note the Build number. Alternatively, via SSH run 'versione' or check /etc/config/version for the exact build version.
    Affected if The installed QTS version matches any of these builds: 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.0.1.2034, 5.0.1.2079, 5.0.1.2131, 5.0.1.2137, 5.0.1.2145, 5.0.1.2173, 5.0.1.2194, 5.0.1.2234, or 5.0.1.2248.
  3. Determine the installed QuTS hero version
    In the web interface, go to Control Panel > System > About and note the Build number. Alternatively, via SSH run 'versione' or check /etc/config/version for the exact build version.
    Affected if The installed QuTS hero version matches any of these builds: h5.1.0.2409, h5.0.1.2045, h5.0.1.2192, h5.0.1.2248, h5.0.1.2269, h5.0.1.2277, h5.0.1.2348, h5.0.1.2376, h4.5.4.1771, h4.5.4.1800, h4.5.4.1813, or h4.5.4.1848.
  4. Check network exposure of the management interface
    Verify whether the QNAP device management interface (ports 8080, 443, or custom ports) is accessible from untrusted networks. Review firewall rules and NAT configurations.
    Affected if The management interface is exposed to the internet or untrusted LAN segments, since the vulnerability can be exploited via network requests without authentication.

The device is affected if it runs any of the specific QTS or QuTS hero build versions listed and has its management interface network-accessible.

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 the specified fixed versions (QTS 5.0.1.2425+, QTS 5.1.0.2444+, QTS 4.5.4.2467+, QuTS hero h5.1.0.2424+, QuTS hero h5.0.1.2515+, or QuTS hero h4.5.4.2476+) to remediate this vulnerability.

Recommended fix High confidence

QTS 5.0.1.2425+, QTS 5.1.0.2444+, QTS 4.5.4.2467+, QuTS hero h5.1.0.2424+, QuTS hero h5.0.1.2515+, or QuTS hero h4.5.4.2476+ depending on current version branch

  1. Identify the current QNAP QTS or QuTS hero version installed on the device
  2. Navigate to the QNAP Control Panel and access the System Update section
  3. For QTS 5.0.x users: Upgrade to QTS 5.0.1.2425 build 20230609 or later
  4. For QTS 5.1.x users: Upgrade to QTS 5.1.0.2444 build 20230629 or later
  5. For QTS 4.5.x users: Upgrade to QTS 4.5.4.2467 build 20230718 or later
  6. For QuTS hero h5.1.x users: Upgrade to h5.1.0.2424 build 20230609 or later
  7. For QuTS hero h5.0.x users: Upgrade to h5.0.1.2515 build 20230907 or later
  8. For QuTS hero h4.5.x users: Upgrade to h4.5.4.2476 build 20230728 or later
Caveat Major version upgrades (e.g., QTS 4.x to 5.x) may have feature or compatibility changes; review QNAP release notes 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-23372 — 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-23372 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