CVE-2020-10625
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 · uneditedWebAccess/NMS (versions prior to 3.0.2) allows an unauthenticated remote user to create a new admin account.
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 confidenceWebAccess/NMS versions prior to 3.0.2 contain an authentication bypass vulnerability that allows unauthenticated remote attackers to create new administrator accounts on the system, effectively granting them full administrative control over the NMS platform.
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< 3.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WebAccess/NMS is installedCheck for WebAccess/NMS installation directories or running services. Common locations include /opt/WebAccess/NMS or C:\WebAccess\NMS on Windows. Look for processes named 'WebAccess' or 'nms' running on the system.Affected if WebAccess/NMS software is present on the system
-
Determine the installed versionLocate the version file or check the application banner. Common paths: /opt/WebAccess/NMS/version, /opt/WebAccess/NMS/build.info, or look at the login page source. On Windows, check the executable properties or registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Advantech\WebAccess\NMS.Affected if The installed version is lower than 3.0.2 (e.g., 3.0.1, 2.0, 1.x)
-
Verify the web management interface is exposedCheck if port 8080, 443, or the default WebAccess/NMS web port is open and listening. Use 'netstat -an | grep -E "(8080|443)"' or check firewall rules.Affected if The web management interface is accessible from network locations (not just localhost)
-
Check for newly created administrator accountsReview administrator accounts in the WebAccess/NMS user management console or database. Look for unexpected accounts created after the initial setup, especially those with 'admin' or 'administrator' privileges.Affected if Unexpected administrator accounts exist that were not created by legitimate administrators
A system is affected if WebAccess/NMS version 3.0.2 or higher is NOT installed and the web management interface is network-accessible.
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.
dbcve · scoped3.0.2
Upgrade WebAccess/NMS to version 3.0.2 or later to remediate this vulnerability. As a compensating control, restrict network access to the management interface to trusted IP addresses only until the upgrade can be performed.
WebAccess/NMS 3.0.2
- 1. Back up the current WebAccess/NMS configuration and database before proceeding with any upgrade.
- 2. Download WebAccess/NMS version 3.0.2 or later from the official vendor source.
- 3. Review the upgrade documentation for any prerequisite requirements.
- 4. Apply the upgrade following the vendor's standard upgrade procedure.
- 5. After upgrade, verify that the authentication mechanism is properly enforced.
- 6. Confirm that unauthenticated users can no longer create admin accounts through the vulnerable endpoint.
- 7. Test that legitimate admin account creation requires proper authentication.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10625 — 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-10625 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