CVE-2020-36194
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 · uneditedAn XSS vulnerability has been reported to affect QNAP NAS running QTS and QuTS hero. If exploited, this vulnerability allows attackers to inject malicious code. This issue affects: QNAP Systems Inc. QTS versions prior to 4.5.2.1566 Build 20210202. QNAP Systems Inc. QuTS hero versions prior to h4.5.2.1638 build 20210414. This issue does not affect: QNAP Systems Inc. QTS 4.5.3.
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 confidenceA Cross-Site Scripting (XSS) vulnerability in QNAP NAS web interface allows authenticated or unauthenticated attackers to inject malicious JavaScript code via unsanitized input parameters. The vulnerability exists in QTS and QuTS hero firmware versions prior to the specified patch dates, enabling session hijacking, credential theft, or phishing attacks against users accessing the NAS management console.
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< 4.5.2.1566< h4.5.2.1638CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify QNAP NAS device on the networkScan network for devices responding on typical QNAP web ports (8080 for HTTP, 443 for HTTPS), or use QNAP Qfinder Pro utility to locate NAS devicesAffected if A QNAP device is found with its web management interface accessible over the network
-
Access the firmware version informationLogin to the QTS or QuTS Hero web interface, then navigate to Control Panel > System > Firmware > Firmware Update, or access the API endpoint at /cgi-bin/authLogin.cgi to retrieve system info including firmware versionAffected if Device is running QTS version prior to 4.5.2.1566 or QuTS Hero version prior to h4.5.2.1638
-
Verify web administration interface is enabledConfirm the NAS web server is running by accessing the login page via HTTP on port 8080 or HTTPS on port 443Affected if The web management interface is accessible (the XSS vulnerability exists in this component)
-
Check if remote access is permittedReview network configuration in Control Panel > System > Network > TCP/IP to determine if the admin interface is bound to WAN/external interfaces or only LANAffected if The web interface is exposed beyond the local network (increases exposure risk for unauthenticated exploitation)
A QNAP NAS is affected if its web interface is accessible and the firmware version is below 4.5.2.1566 (QTS) or below h4.5.2.1638 (QuTS Hero).
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data4.5.2.1566
Apply the vendor-supplied firmware updates: upgrade QTS to version 4.5.2.1566 Build 20210202 or later (or 4.5.3+), and QuTS hero to version h4.5.2.1638 Build 20210414 or later. If immediate patching is not possible, restrict administrative interface access to trusted networks or VPN.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2020-36194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-36194 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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