dbcve.org
Maxpro Nvr Xe FirmwareOperating system · Honeywell

CVE-2020-6960

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-22
Fix available
A fix is available. Upgrade to after 5.6 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
The following versions of MAXPRO VMS and NVR, MAXPRO VMS:HNMSWVMS prior to Version VMS560 Build 595 T2-Patch, HNMSWVMSLT prior to Version VMS560 Build 595 T2-Patch, MAXPRO NVR: MAXPRO NVR XE prior to Version NVR 5.6 Build 595 T2-Patch, MAXPRO NVR SE prior to Version NVR 5.6 Build 595 T2-Patch, MAXPRO NVR PE prior to Version NVR 5.6 Build 595 T2-Patch, and MPNVRSWXX prior to Version NVR 5.6 Build 595 T2-Patch contain an SQL injection vulnerability that could give an attacker remote unauthenticated access to the web user interface with administrator-level privileges.

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 confidence

SQL injection vulnerability in MAXPRO VMS and NVR web interfaces allows remote unauthenticated attackers to gain administrator-level privileges. The flaw is exploitable without authentication, enabling complete compromise of the video management system.

MitigationUpgrade to MAXPRO VMS VMS560 Build 595 T2-Patch or later, or NVR 5.6 Build 595 T2-Patch or later. If immediate patching is not possible, restrict network access to the web interface and monitor for suspicious SQL patterns in requests.

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
Maxpro Nvr Xe FirmwareOperating system
Affected:<= 5.6
Maxpro Nvr Se FirmwareOperating system
Affected:<= 5.6
Maxpro Nvr Pe FirmwareOperating system
Affected:<= 5.6
Mpnvrswxx FirmwareOperating system
Affected:<= 5.6
Hnmswvms FirmwareOperating system
Affected:<= vms560
Hnmswvmslt FirmwareOperating system
Affected:<= vms560

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. Identify the MAXPRO NVR or VMS firmware version
    Access the device admin panel or check system information page in the web interface; look for firmware version number displayed (e.g., 5.6 or earlier for NVR models, vms560 or earlier for VMS models)
    Affected if The displayed firmware version is 5.6 or lower for NVR models (Xe/Se/Pe), or vms560 or lower for VMS models (hnmswvms, hnmswvmslt)
  2. Confirm the web interface is accessible
    Attempt to reach the device web interface over HTTP/HTTPS (typically ports 80, 443, or 8080); verify the login page loads
    Affected if The web interface responds and presents a login page, indicating it is enabled and exposed on the network
  3. Check for unauthorized administrator accounts
    Log into the web interface with administrator credentials and review the user account list under User Management or Users settings; look for unfamiliar accounts with administrator privileges
    Affected if Unexpected administrator-level accounts exist that were not created by your organization, indicating potential exploitation

Your environment is affected if the MAXPRO NVR or VMS web interface is accessible and the firmware version is 5.6 or lower (NVR) or vms560 or lower (VMS), as this enables unauthenticated SQL injection exploitation.

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 a release after 5.6
Interim mitigation

Upgrade to MAXPRO VMS VMS560 Build 595 T2-Patch or later, or NVR 5.6 Build 595 T2-Patch or later. If immediate patching is not possible, restrict network access to the web interface and monitor for suspicious SQL patterns in requests.

Recommended fix High confidence

NVR 5.6 Build 595 T2-Patch (for NVR products) or VMS560 Build 595 T2-Patch (for VMS products)

  1. Identify the specific MAXPRO product (NVR XE, NVR SE, NVR PE, MPNVRSWXX, HNMSWVMS, or HNMSWVMSLT) and current firmware version
  2. Obtain the fixed firmware version from the vendor (Honeywell): NVR 5.6 Build 595 T2-Patch for NVR products, or VMS560 Build 595 T2-Patch for VMS products
  3. Review vendor documentation for firmware upgrade instructions specific to your device
  4. Apply the firmware upgrade following the vendor's standard upgrade procedure
  5. After upgrade, verify the firmware version matches the fixed release (NVR 5.6 Build 595 T2-Patch or VMS560 Build 595 T2-Patch)
  6. Confirm the SQL injection vulnerability is remediated by verifying the web interface is accessible and the specific injection point is no longer vulnerable
Caveat Review vendor release notes for any configuration or feature changes between versions before upgrading

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

Fix this in Maxpro Nvr Xe Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-6960 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