CVE-2017-16736
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 Unrestricted Upload Of File With Dangerous Type issue was discovered in Advantech WebAccess versions prior to 8.3. WebAccess allows a remote attacker to upload arbitrary files.
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 confidenceAdvantech WebAccess versions prior to 8.3 contain an unrestricted file upload vulnerability that allows remote attackers to upload arbitrary files to the server. This can potentially enable remote code execution if executable files (e.g., web shells) are uploaded and subsequently accessed.
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< 8.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Confirm Advantech WebAccess installationLook for WebAccess installation directories (commonly in C:\Advantech\WebAccess or C:\Inetpub\wwwroot\BroadWeb) or check Windows Programs and Features for 'Advantech WebAccess' entryAffected if Advantech WebAccess is not found on the system, the system is not affected by this specific vulnerability
-
Determine installed WebAccess versionCheck the version of Advantech WebAccess via the Windows Programs and Features list, or look for version information in the WebAccess installation directory (often in a README, version.txt, or the main executable properties)Affected if The installed version number is lower than 8.3 (for example, 8.2, 8.1, 8.0, or earlier)
-
Verify file upload functionality is accessibleCheck if the WebAccess upload endpoints are exposed and accessible. This typically involves checking the web server configuration (IIS) for WebAccess virtual directories and whether authentication is required for upload-related paths (such as /upload, /fileupload, or similar endpoints)Affected if The file upload functionality is accessible without proper authentication or validation (this is required for the vulnerability to be exploitable)
-
Review web root configurationInspect the web server (IIS) configuration to determine if uploaded files can be stored within the web root directory where they could be executed via HTTP requestsAffected if Upload directories are configured inside the web root and script execution is not disabled in those directories
The system is affected if Advantech WebAccess version 8.3 or earlier is installed AND the file upload feature is accessible without proper restrictions.
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 data8.3
Upgrade to WebAccess version 8.3 or later which contains the security fix. As an interim measure, implement strict file type validation (extension and MIME type), enforce authentication on upload endpoints, store uploads outside the web root, and disable script execution in upload directories.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16736 — 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-16736 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