Webaccess\/nmsApplication · Advantech

CVE-2020-10621

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-09
Fix available
A fix is available. Upgrade to 3.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Multiple issues exist that allow files to be uploaded and executed on the WebAccess/NMS (versions prior to 3.0.2).

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

Multiple critical vulnerabilities in WebAccess/NMS versions prior to 3.0.2 allow unauthenticated attackers to upload arbitrary files to the server and subsequently execute them, leading to remote code execution. The combination of unrestricted file upload and execution capability yields the critical 9.8 CVSS score.

MitigationUpgrade WebAccess/NMS to version 3.0.2 or later to remediate these file upload/execution vulnerabilities.

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
Webaccess\/nmsApplication
Affected:< 3.0.2

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm WebAccess/NMS is installed
    Locate WebAccess/NMS installation directories or running services. Common locations include C:\WebAccess or C:\Program Files\WebAccess on Windows, or /opt/WebAccess on Linux. Check for processes named 'WebAccess' or 'NMS' in task manager or process list.
    Affected if WebAccess/NMS software is found installed on the system
  2. Identify installed version
    Check the version of WebAccess/NMS by examining the software version information, typically found in the installation directory, the service properties, or the About page of the web interface if accessible.
    Affected if The installed version is lower than 3.0.2 (e.g., 3.0.1, 2.x, 1.x)
  3. Verify web interface is accessible
    Determine if the WebAccess/NMS web interface port is listening and reachable. Common ports are 80, 443, or 8080. Use 'netstat -an' or equivalent to check for listening services.
    Affected if The web interface port is open and accepting connections
  4. Check for file upload endpoints
    Inspect the web application's available endpoints or URLs that handle file uploads. Look for upload-related paths in the web server configuration or application logs.
    Affected if File upload functionality is exposed via the web interface without proper restrictions
  5. Review authentication configuration
    Examine whether the file upload functionality requires authentication or can be accessed anonymously. Check the access control settings in the WebAccess/NMS configuration.
    Affected if Unauthenticated access to file upload features is permitted

A system is affected if WebAccess/NMS version is installed and is lower than 3.0.2, with the web interface accessible and file upload functionality exposed.

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
Upgrade available Upgrade to 3.0.2 or later
Fixed in 3.0.2
Interim mitigation

Upgrade WebAccess/NMS to version 3.0.2 or later to remediate these file upload/execution vulnerabilities.

Recommended fix Moderate confidence

3.0.2

  1. Upgrade WebAccess/NMS to version 3.0.2 or later to remediate the unrestricted file upload vulnerability

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

Fix this in Webaccess\/nms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10621 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10621 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