CVE-2017-13072
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 · uneditedCross-site scripting (XSS) vulnerability in App Center in QNAP QTS 4.2.6 build 20171208, QTS 4.3.3 build 20171213, QTS 4.3.4 build 20171223, and their earlier versions could allow remote attackers to inject Javascript code.
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 confidenceA cross-site scripting (XSS) vulnerability exists in the App Center component of QNAP QTS firmware versions 4.2.6 (build 20171208), 4.3.3 (build 20171213), 4.3.4 (build 20171223), and earlier versions. The vulnerability allows remote attackers to inject malicious JavaScript code, likely through unsanitized user input in the App Center interface.
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.2.6= 4.3.3= 4.3.4CVSS 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.0/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 QTS firmware versionLog into the QNAP admin interface and navigate to Control Panel > System > Firm Update, or use the Qfinder Pro tool to determine the installed firmware version. Alternatively, access the NAS via SSH and run 'cat /proc/ fw_info' or check the version displayed on the login page.Affected if The installed version matches 4.2.6, 4.3.3, 4.3.4, or any version earlier than these builds.
-
Confirm App Center component is accessibleVerify that the App Center application is available and enabled on the QNAP device. Access the App Center through the QTS desktop or by navigating to the App Center URL if the interface allows direct access.Affected if The App Center component is present and accessible to users or administrators.
-
Verify App Center administrative accessDetermine whether the App Center administrative interface is exposed to network access. Check if the QNAP device is accessible on the local network and whether the App Center can be reached via HTTP/HTTPS without requiring full admin authentication, or if unauthenticated or low-privilege users can access App Center functions.Affected if The App Center interface is network-accessible and accepts user input without proper sanitization controls.
A user is affected if the QNAP QTS firmware version is 4.2.6, 4.3.3, 4.3.4, or any earlier version, and the App Center component is accessible for interaction.
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 dataApply the vendor-supplied firmware update from QNAP to patch the XSS vulnerability. Until patched, restrict access to the App Center administrative interface to trusted users only.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13072 — 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-2017-13072 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